ReplyNodes

Quickstart

This guide takes you from no account to a successful request. Pick one path:

PathUse it whenNeeds a keySetup
KeylessYou want to try ReplyNodes right nowNoNone
API keyYou are calling the REST API from code or CIYesCreate a key
MCPYou want tools inside an MCP clientOAuth or keyAdd the server URL

ReplyNodes uses three hosts. api.replynodes.com is the REST API. md.replynodes.com and brand.replynodes.com are free keyless endpoints for Markdown and brand data. mcp.replynodes.com is the MCP server.

Option 1: No key

These work without an account. Limits are per caller per UTC day (see Limits and pricing).

curl -sS 'https://md.replynodes.com/example.com'
curl -sS 'https://brand.replynodes.com/stripe.com'
curl -sS 'https://api.replynodes.com/v1/youtube/video/dQw4w9WgXcQ'

The first call returns the page as Markdown. When a call is over its daily limit it returns 429 anonymous_limit_reached, and the body tells you how to get a key. See Errors for an example.

Option 2: API key

  1. Sign in on the ReplyNodes dashboard.

  2. Open the API keys page and create a key. A key is shown once, so copy it now.

  3. Store it as REPLYNODES_API_KEY in your secret store or shell. Do not commit it or put it in browser code.

    export REPLYNODES_API_KEY="paste-your-key-here"
  4. Make your first request:

    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 looks like this (abridged; data.links, data.images and data.metadata are shortened here):

{
  "data": {
    "url": "https://example.com",
    "title": "Example Domain",
    "markdown": "# Example Domain\n\nThis domain is for use in documentation examples…",
    "metadata": { "title": "Example Domain", "language": "en", "url": "https://example.com" },
    "links": [],
    "images": [],
    "truncated": false,
    "markdown_chars": 167
  },
  "meta": { "request_id": "req_…" }
}

Field names and types come from the API reference. Values are illustrative. meta.request_id is always present and is also returned in the X-Request-Id header.

If something goes wrong

Errors use { "error": { "code", "message", "request_id" } }. These are the most common ones:

SymptomLikely causeFix
401The key is missing, expired or supersededCheck the Authorization: Bearer header and create or rotate a key
402 topup_requiredThe workspace is out of creditsAdd credits on the billing page
429Rate limit or daily limit reachedWait for Retry-After, then retry once
400 invalid_requestA parameter is missing or invalidCompare your request with the API reference

The full list is on the Errors page.

Correlate requests

Send an opaque X-Request-Id when you want to connect a client log to a support investigation:

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

Option 3: MCP client

Add https://mcp.replynodes.com/mcp as a remote server in your client. Clients that support OAuth sign you in through the browser, and no organization id is needed. For headless clients and CI, send your API key as a Bearer header. See MCP for each client.

Next steps

I want toGo to
Understand keys, scopes and OAuthAuthentication
Read a specific sourceGuides
Look up every parameterAPI reference
Handle errors and limitsErrors, Limits and pricing
Build an agent that starts without a keyAgent quickstart

On this page