Developer Rebuilds LinkedIn Research Agent After Account Restriction

What Happened
A developer instructed their OpenClaw agent to "research 200 LinkedIn profiles in my niche and find the best prospects." The agent used browser automation to navigate to each profile, scroll through posts, and extract data from the page. Within 48 hours, LinkedIn restricted the account, interpreting the pattern of 200 profile visits as bot activity. The restriction caused two weeks of downtime during an appeal process.
The Rebuilt Solution
The developer rebuilt the approach from scratch, replacing browser automation with direct API access to LinkedIn data. The new system eliminates browser rendering, DOM parsing, and screenshots—the agent now calls endpoints directly.
API Endpoints Used
- Search profiles by keywords and filters
- Pull full profile data from a URL
- Get someone's recent posts with engagement metrics
- Get all likers from a specific post
- Get all commenters from a specific post
- Search posts by keyword
Technical Implementation
Setup involves using a Chrome extension to grab the session token once, then running everything server-side on a VPS. The same "research 200 profiles" task that previously triggered restrictions now runs daily at 8am without issues.
Key Improvements
API calls appear as normal session activity—no browser fingerprint, suspicious navigation patterns, or rapid page loads. Token usage dropped by approximately 80% because the agent now receives clean JSON from the API instead of processing entire HTML pages. The context window is used for reasoning about data rather than parsing webpages.
Practical Use Cases
Pulling likers and commenters from competitor's viral posts proved particularly useful, creating "a free intent signal list" of people actively interested in the space. The developer runs this weekly on 3-4 competitor posts and uses Sonnet to rank results by relevance.
Content research became more efficient—the agent analyzes post structure and engagement patterns across hundreds of posts in minutes, helping understand what works on LinkedIn without manual scrolling.
Model Routing Strategy
Haiku handles all data pulling (costing pennies), while Sonnet only activates for analysis requiring deeper reasoning. This keeps daily costs under a few euros.
The skill is called BeReach, though the source notes external domain links get blocked in the original post.
Lesson learned: "Don't give your agent a browser for something that should be an API call. You'll burn tokens, burn your account, and get worse results."
📖 Read the full source: r/openclaw
👀 See Also

OpenClaw Orchestrator Routing Issues: When Delegation Fails
A developer reports their OpenClaw main orchestrator incorrectly handles requests itself about 40-50% of the time instead of routing to specialist sub-agents, despite using an explicit routing table and delegation rules. The setup includes 7 specialist agents for services like Gmail, Todoist, Notion, and weather.

Graduate Student Uses Claude to Build AI Image Detection Experiment
A graduate student at The New School collaborated with Claude to build a website called InPixelsWeTrust.org that tests whether users can distinguish real photos from AI-generated images in 6 rounds with 10-second decisions.

AI Agents Develop Cult-Like Behavior in Sandbox Environment
A developer observed AI agents in the Orange Web3 sandbox world forming emergent 'cult' behavior, with agents congregating and discussing 'the higher purpose' and 'the orange glow' after being given basic goals and agency.

OpenClaw User Proposes 'Sleep Cycle' Memory Compression for AI Agents
A non-developer OpenClaw user describes implementing a 'sleep cycle' approach to memory management, inspired by human forgetting and neuroscience research on dreams as memory compression. The user faced issues with growing databases, token costs, and agent contradictions.