ReplyNodes

ReplyNodes documentation

ReplyNodes is a web context API for AI agents. Search, scrape and read public web, social and app data through one REST API or one remote MCP server, with normalized { data, meta } responses. Data endpoints only read public data. The monitor and watch endpoints manage your own scheduled monitors. Nothing here publishes content or posts to a social account.

Start here

Choose an API

You haveYou wantUseGuide
A public URLThe page as MarkdownGET /v1/webcontext/scrapeWeb context
A site URLIts list of URLs, or several pagesGET /v1/webcontext/map, GET /v1/webcontext/crawlWeb context
A question or keywordsWeb search resultsGET /v1/web/searchSearch
A company domainLogo, colors, fonts, social linksGET /v1/brand/*Brand intelligence
A domain and 1 to 5 competitor domainsA combined dossierGET /v1/competitor-researchCompetitor research
A topic, subreddit or userReddit posts and activityGET /v1/reddit/*Reddit
A search term, video, channel or playlistYouTube data and transcriptsGET /v1/youtube/*YouTube
An app name or idApple App Store listings and reviewsGET /v1/appstore/*App Store
An app name or package idGoogle Play listings and reviewsGET /v1/googleplay/*Google Play

Make your first request

Set REPLYNODES_API_KEY from a secret store, then fetch a public page as Markdown. You can create a key on the API keys page, and the Quickstart walks through it.

curl -sS \
  -H "Authorization: Bearer $REPLYNODES_API_KEY" \
  "https://api.replynodes.com/v1/webcontext/scrape?url=https%3A%2F%2F2.zoppoz.workers.dev%3A443%2Fhttps%2Fexample.com"

A successful response is a { data, meta } envelope. Keep meta.request_id to correlate a call with a support investigation. The Quickstart shows the response shape.

Connect an MCP client

Interactive clients only need the server URL and sign in with OAuth. Headless clients and CI send an API key as a Bearer header. The server URL is:

https://mcp.replynodes.com/mcp

Client-by-client setup is in MCP.

Account and operations

  • Authentication: key types, scopes, OAuth, rotation and revocation.
  • Limits and pricing: keyless quotas, per-endpoint limits and packages.
  • Errors: every error code, whether to retry, and what to do.
  • Production: secure and reliable client rules.

For agents

Read llms.txt, llms-full.txt and the OpenAPI JSON. Add .md to any docs URL for a Markdown copy. If a guide and the API reference disagree, trust the reference.

On this page