Quickstart
This guide takes you from no account to a successful request. Pick one path:
| Path | Use it when | Needs a key | Setup |
|---|---|---|---|
| Keyless | You want to try ReplyNodes right now | No | None |
| API key | You are calling the REST API from code or CI | Yes | Create a key |
| MCP | You want tools inside an MCP client | OAuth or key | Add 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
-
Sign in on the ReplyNodes dashboard.
-
Open the API keys page and create a key. A key is shown once, so copy it now.
-
Store it as
REPLYNODES_API_KEYin your secret store or shell. Do not commit it or put it in browser code.export REPLYNODES_API_KEY="paste-your-key-here" -
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:
| Symptom | Likely cause | Fix |
|---|---|---|
401 | The key is missing, expired or superseded | Check the Authorization: Bearer header and create or rotate a key |
402 topup_required | The workspace is out of credits | Add credits on the billing page |
429 | Rate limit or daily limit reached | Wait for Retry-After, then retry once |
400 invalid_request | A parameter is missing or invalid | Compare 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 to | Go to |
|---|---|
| Understand keys, scopes and OAuth | Authentication |
| Read a specific source | Guides |
| Look up every parameter | API reference |
| Handle errors and limits | Errors, Limits and pricing |
| Build an agent that starts without a key | Agent quickstart |