No token or crypto affiliation: Agent Reach has no official token, coin, investment product, fee-claim program, wallet connection, or Solana/Pump.fun project. Any crypto project using the Agent Reach name, GitHub URL, or author identity is not affiliated with this repository. Do not connect a wallet or claim fees based on messages, posts, or links that say otherwise.
BrowserAct extracts any data you need from complex websites such as Amazon, LinkedIn, X, and Google Maps. Simply describe your extraction request in natural language, and its Agent will explore and test page flows in a real browser, generate a reliable reusable data-collection Bot, and return structured results. There is no need to build a scraper or write code. Built-in stealth browsing, CAPTCHA handling, and high-quality residential proxies help make complex web data extraction more reliable. New users receive 1,000 credits upon registration. Try it free now.
Deploy OpenClaw on Tencent Cloud Lighthouse in seconds, connect Agent Reach through chat, and add internet access to your OpenClaw setup.
CoreClaw | Web scraping platform and ready-made data collection tools. CoreClaw provides 100+ ready-made data collection tools for Amazon, TikTok, Google Maps, Instagram, Facebook, YouTube, and more. No code required, with JSON/CSV exports and billing only for successful results. Free $3 trial!
AstraFlow ModelVerse provides one-click access to 200+ models, including leading open-source models such as Kimi K3, DeepSeek V4/V3, Qwen 3, GLM5.2, and happyhorse. No training required—ready to use out of the box.
Why Agent Reach?
AI Agents can already access the internet — but “can go online” is barely the start.
The most valuable information lives across social and niche platforms: Twitter discussions, Reddit feedback, YouTube tutorials, XiaoHongShu reviews, Bilibili videos, GitHub activity… These are where information density is highest, but each platform has its own barriers:
Pain Point
Reality
Twitter API
Pay-per-use, moderate usage ~$215/month
Reddit
Server IPs get 403’d
XiaoHongShu
Login required to browse
Bilibili
Blocks overseas/server IPs
To connect your Agent to these platforms, you’d have to find tools, install dependencies, and debug configs — one by one.
All tools are open source, all APIs are free. The only possible cost is a server proxy ($1/month) — local computers don’t need one
🔒 Privacy safe
Cookies stay local. Never uploaded. Fully open source — audit anytime
🔄 Kept up to date
Every platform routes through a primary + fallback backend list. When an access path dies, we switch to the next — you won’t notice (June 2026: Bilibili 412-blocked yt-dlp → switched to bili-cli, zero action on your side)
🤖 Works with any Agent
Claude Code, OpenClaw, Cursor, Windsurf… any Agent that can run commands
🩺 Built-in diagnostics
agent-reach doctor — one command shows what works, what doesn’t, and how to fix it
No zero-config path (anonymous endpoints blocked). Desktop: OpenCLI via browser session; or rdt-cli + cookie
Setup levels: Zero config = install and go · Auto-configured = handled during install · mcporter = needs MCP service · Cookie = export from browser · Proxy = $1/month
Quick Start
⚠️ OpenClaw users: enable exec permission first
Agent Reach relies on the Agent running shell commands (pip install, mcporter, twitter, etc.). If your OpenClaw uses the default messaging tool profile, the Agent won’t be able to run them. Enable exec before installing:
openclaw config set tools.profile "coding"
Or set "tools": { "profile": "coding" } in ~/.openclaw/openclaw.json. After changing it, restart the Gateway (openclaw gateway restart) and start a new conversation. Other platforms (Claude Code, Cursor, Windsurf, etc.) are not affected.
Copy this to your AI Agent (Claude Code, OpenClaw, Cursor, etc.):
After the Skill is installed, the Agent will auto-detect whether agent-reach CLI is available and install it if needed.
If you explicitly install external tools with agent-reach install --system, the skill is registered automatically. The default read-only check leaves existing files unchanged.
Prefer an English-only skill file? Set an English locale or export AGENT_REACH_LANG=en
before running agent-reach install --env=auto --system or agent-reach skill --install.
The installed file is always written as SKILL.md, so switching languages means rerunning
the install command with the new locale and replacing the previously installed skill file.
Works Out of the Box
No configuration needed — just tell your Agent:
“Read this link” → curl https://r.jina.ai/URL for any web page
“What’s this GitHub repo about?” → gh repo view owner/repo
“What does this video cover?” → yt-dlp --dump-json URL for subtitles
“Read this tweet” → set TWITTER_AUTH_TOKEN / TWITTER_CT0, then run twitter tweet URL
“Subscribe to this RSS” → feedparser to parse feeds
No commands to remember. The Agent reads SKILL.md and knows what to call.
Unlock on Demand
Don’t use it? Don’t configure it. Every step is optional.
🍪 Cookies — Free, 2 minutes
Tell your Agent “help me configure Twitter cookies” — it’ll guide you through a
manual Cookie-Editor export. Agent Reach saves the values for doctor to check
whether credentials are present; doctor does not run twitter status.
Direct twitter commands still require TWITTER_AUTH_TOKEN and TWITTER_CT0
in their process environment.
For XiaoHongShu, Agent Reach never logs the user in or reads browser cookies.
OpenCLI may use only an existing Chrome session explicitly controlled by the
user. If none exists, do not automate login; use a manual Cookie-Editor export
with xiaohongshu-mcp or a legacy tool. agent-reach configure xhs-cookies
does not inject cookies into OpenCLI or Chrome.
🌐 Proxy — $1/month, restricted networks only
Most users need no proxy. If your network blocks Reddit/Twitter (e.g. mainland China) get one (Webshare recommended, $1/month) and send the address to your Agent — it saves it and exports HTTP(S)_PROXY when calling those tools.
Reddit needs a logged-in session either way — OpenCLI rides your browser session, or rdt-cli after rdt login. Bilibili works via bili-cli without a proxy.
Status at a Glance
$ agent-reach doctor
👁️ Agent Reach Status
========================================
✅ Ready to use:
✅ GitHub repos and code — public repos readable and searchable
✅ YouTube video subtitles — yt-dlp
✅ Bilibili search & video detail — bili-cli (subtitles via OpenCLI)
✅ RSS/Atom feeds — feedparser
✅ Web pages (any URL) — Jina Reader API
🔍 Search (free Exa key to unlock):
⬜ Web semantic search — sign up at exa.ai for free key
🔧 Configurable:
⚠️ Twitter/X — doctor checks only that explicit credentials exist; direct CLI still needs its environment variables
⬜ Reddit posts and comments — needs login: rdt-cli after `rdt login`, or OpenCLI browser session
⬜ XiaoHongShu notes — OpenCLI needs an existing user-controlled session; otherwise use Cookie-Editor with MCP/legacy tools
⬜ Facebook / Instagram — desktop: OpenCLI browser session
Status: 6/9 channels available
Design Philosophy
Agent Reach is a capability layer, not yet another tool.
It sits one level above any specific implementation — it handles selection, installation, health checks, and routing, not the reading itself. Reading is done by your Agent calling upstream tools directly; there is no wrapper layer.
Every time you spin up a new Agent, you spend time finding tools, installing deps, and debugging configs — what reads Twitter? How do you log into Reddit? What replaces a discontinued XiaoHongShu CLI? Every time, you re-do the same work. Agent Reach does one simple thing: the most reliable access path for each platform, chosen, installed, and health-checked for you. Access paths come and go (in March 2026 a batch of single-platform CLIs went unmaintained — we re-routed), so you don’t have to care.
🔌 Every platform = an ordered backend list (primary + fallbacks)
Switching access paths means reordering the list, not rewriting code. agent-reach doctor tells you which backend each platform is currently using.
Each channel file actually probes its candidate backends in order (not just checking that a command exists) — the first fully working one becomes the active backend, and broken ones come with a fix prescription. The actual reading and searching is done by the Agent calling the upstream tools directly.
📌 These are the current choices, re-verified regularly on real machines. When a path dies we switch to the next — agent-reach doctor always tells you which one is active.
Agent Skills Hub — Find Claude skills & MCP servers without guessing what’s safe. Every one of 133,000+ entries is security-graded, quality-scored, and refreshed every 8 hours.
AtomGit mirror — Synchronized AtomGit mirror for Agent Reach.
