ReplyNodes documentation

ReplyNodes is the read-only web context API for AI agents: search, scrape and read public web, social and app data through one REST API or remote MCP server. The data endpoints read public data. The monitor and watch endpoints manage your own scheduled monitors; nothing here publishes content or posts to social accounts.

Start here

• Introduction: what ReplyNodes is and how the pieces fit together.
• Quickstart: make your first real read in under a minute.
• Agent quickstart: choose REST, an SDK, MCP or an agent skill for your client.
• Authentication: MCP OAuth for interactive clients, API keys for headless and REST use.
• MCP setup: connect the remote MCP server at https://mcp.replynodes.com/mcp.
• API reference: every operation, generated from the canonical OpenAPI document.

Provider guides

• Web context: scrape, map and crawl public web pages.
• Search: web search for agents.
• Brand intelligence and Brand Kit: logos, colors, fonts and social links from a domain.
• YouTube, Reddit, Apple App Store and Google Play: public data for research agents.
• PDF: turn a PDF into Markdown for an agent.

Machine-readable

Agents can read llms.txt, the full text in llms-full.txt, a Markdown copy of every page (add .md to a docs URL) and the OpenAPI JSON. The product site is replynodes.com.

Use the documentation pages to plan a request, then verify the final operation against the deployed capability and OpenAPI documents. A typical agent workflow is to discover a public resource, retain its identifier and relevant locale, request a bounded detail or enrichment response, and pass the normalized result to the next step. Keep the returned request_id with the result so failures and upstream changes can be correlated later. Public provider data can be incomplete, stale, removed, or temporarily unavailable; clients should communicate that uncertainty instead of filling gaps with guessed values.

ReplyNodes is a read-only data layer. The documented routes do not publish content, modify external listings, access private accounts, or forward browser sessions. Use finite timeouts and retries, honor Retry-After on rate limits, and avoid turning a health check into a broad crawl. If a guide and a live contract disagree, trust the live contract and report the documentation mismatch for correction.