Build on ReplyNodes with our public REST API and documented connection workflows.
ReplyNodes is read-only public data at https://api.replynodes.com. The preferred remote MCP endpoint is https://mcp.replynodes.com/mcp. Native MCP OAuth uses https://auth.replynodes.com with mcp:read; headless/manual clients use an rn_test_ or rn_live_ API key. No write or mutation tools are exposed.
| Client | Protocol | Endpoint | Auth | Setup |
|---|---|---|---|---|
| Claude Code, Codex, Claude, Hermes, OpenClaw | Remote MCP | https://mcp.replynodes.com/mcp | OAuth mcp:read or rn_test_/rn_live_ Bearer key | MCP config → |
| Applications and GPT Actions | REST API | https://api.replynodes.com | Authorization: Bearer $REPLYNODES_API_KEY | REST quickstart → |
Use a ReplyNodes API key as a Bearer token in the Authorization header. Sign in at https://platform.replynodes.com/sign-in and create or manage the key at https://platform.replynodes.com/api-keys.
Retrieve normalized web, brand, app-store, video, community, and scraped data through the canonical read-only API. Discover current providers, routes, and schemas from GET https://api.replynodes.com/v1/capabilities.
Connect an MCP client to https://mcp.replynodes.com/mcp with a workspace Read API key using the Bearer authentication format documented for MCP.
The public API and remote MCP surface expose read-only provider operations. They do not create, update, delete, schedule, or otherwise mutate provider data.
Use the agent setup guides for current read-only REST and MCP integration instructions.
OpenAPI publication status → The OpenAPI 3.0.3 document (v1) is published at docs.replynodes.com/api/openapi.json with an interactive reference at docs.replynodes.com/reference, and is returned inline by GET https://api.replynodes.com/v1/capabilities.