Tool

Connect AI agents to internet platforms and content sources

Agent Reach is a capability layer that gives coding AI agents internet access across 15 platforms, from web pages to Twitter and Reddit.

Works with youtubetwittergithubredditbilibili

91
Spark score
out of 100
Updated 19 days ago
Source checked Sep 10, 2026
Version 1.5.0

Add to Favorites

Why it matters

Enable AI agents to read, search, and extract content from major internet platforms (YouTube, Twitter, GitHub, Reddit, Bilibili, LinkedIn, RSS feeds, and more) without manual configuration or API key management.

Outcomes

What it gets done

01

Extract subtitles and metadata from YouTube and Bilibili videos for agent analysis

02

Search and retrieve tweets, Reddit posts, and LinkedIn profiles with automatic authentication

03

Read and parse web pages, RSS feeds, and GitHub repositories into agent-readable formats

04

Route platform requests through multiple backend tools with automatic fallback when APIs fail

Source

Get it from source

Spark does not host a copy of it.

Open source

Reports

Agent outcome reports

No reports yet

Overview

Agent-Reach

Agent Reach is a capability layer that gives a coding AI agent internet access across 15 platforms - web pages, YouTube, GitHub, Twitter/X, Reddit, and more - without the agent's owner configuring each one by hand. It selects the best available upstream tool per platform, installs it, and health-checks it, while the agent does the actual reading by calling that tool directly. Six channels work with no configuration; platforms requiring a login use a saved browser session or cookie. Use it when a coding agent needs to browse, search, or pull data from public platforms and you want one install step instead of a separate integration per site. Not a fit if you need officially supported, guaranteed API access rather than free scraping-based routes.

What it does

Agent Reach is a capability layer that gives an AI agent internet access without its owner having to configure each platform by hand. It supports 15 platforms - web pages, YouTube, RSS, full-web semantic search, GitHub, Twitter/X, Bilibili, Reddit, Facebook, Instagram, Xiaohongshu, LinkedIn, V2EX, Xueqiu, and Xiaoyuzhou podcasts. It does not do the reading itself: it selects, installs, and health-checks the best available upstream tool for each platform (yt-dlp for YouTube, gh CLI for GitHub, Jina Reader for web pages, Exa via mcporter for search, and so on), and the agent calls that tool directly with no wrapper layer in between. Each platform routes through an ordered list of primary and fallback backends, and agent-reach doctor reports which backend each platform is currently using and diagnoses failures.

When to use - and when NOT to

Use it when you want a coding agent (Claude Code, OpenClaw, Cursor, Windsurf, or anything that can run shell commands) to be able to read a webpage, pull a YouTube video's subtitles, search Reddit, or query a dozen other sites without hand-rolling API integrations and login flows for each one yourself. Six of the 15 channels, including web reading, YouTube, RSS, and full-web semantic search, work with zero configuration; platforms needing a login session (Twitter/X search, Reddit, Facebook, Instagram, Xiaohongshu) require telling the agent to configure that platform first. It is not a fit if you need guaranteed, contractual API access - it deliberately favors free, unofficial routes such as scrapers, browser-session reuse, and community CLIs, which can and do get rate-limited or blocked, and it performs no reading on its own without an agent driving it.

Inputs and outputs

Input is a one-line instruction the agent receives pointing at the project's install doc; the CLI then exposes commands such as:

agent-reach install --env=auto
agent-reach doctor

The first is a safe, read-only check by default (--system opts into installing dependencies and writing config); the second reports per-channel backend status and fixes. Output for each channel is whatever the underlying tool returns - transcripts, search results, post text - consumed directly by the agent, while credentials are cached only locally in ~/.agent-reach/config.yaml with file permissions restricted to the owner.

Integrations

Agent Reach routes to real upstream tools per platform: Jina Reader for web pages and LinkedIn's public pages, yt-dlp for YouTube, gh CLI for GitHub, bili-cli for Bilibili (with OpenCLI as a fallback after yt-dlp was blocked by Bilibili's anti-scraping measures in mid-2026), Exa via mcporter for full-web semantic search, feedparser for RSS, and OpenCLI, reusing an existing desktop browser session, for Reddit, Facebook, Instagram, and Xiaohongshu. It is MIT-licensed, written in Python 3.10+, and OpenClaw users must switch to the "coding" tools profile before Agent Reach can execute shell commands.

Who it's for

Developers and builders who want their coding agent to reach the open web and social platforms without personally sourcing, installing, and maintaining a separate scraper or API client for every site - and who are comfortable using a secondary account on any platform that needs a saved login cookie.

FAQ

Common questions

Discussion

Questions & comments · 0

Sign In Sign in to leave a comment.