# ReplyNodes Read API skill

ReplyNodes provides read-only public data for agents at `https://api.replynodes.com`.
There are no social publishing, write, mutation, or platform-account tools on this API.

## Authentication

For headless/manual access, use a ReplyNodes API key beginning with `rn_test_` or `rn_live_` as a Bearer token. If you do not have one, follow the browser-approved claim flow at [`auth.md`](https://replynodes.com/auth.md), then store the returned key as `REPLYNODES_API_KEY`. Organization context is resolved from the authenticated key; clients do not send an organization id.

```sh
curl -sS https://api.replynodes.com/v1/capabilities \
  -H "Authorization: Bearer ${REPLYNODES_API_KEY}" \
```

The capabilities response is the source of truth for current providers, routes, schemas, read-only status, and billing. Only call routes whose `callable` value is true; use their documented HTTP method and parameters.

## Preferred remote MCP

Remote MCP is available at `https://mcp.replynodes.com/mcp`. Headless/manual clients send an `rn_test_` or `rn_live_` API key using an `Authorization` header with the `Bearer` scheme. Clients that support native MCP OAuth use Better Auth issuer `https://auth.replynodes.com` with scope `mcp:read`.

### Claude Code

```json
{
  "mcpServers": {
    "replynodes": {
      "url": "https://mcp.replynodes.com/mcp",
      "headers": {
        "Authorization": "Bearer ${REPLYNODES_API_KEY}"
      }
    }
  }
}
```

### Codex

```toml
[mcp_servers.replynodes]
url = "https://mcp.replynodes.com/mcp"
[mcp_servers.replynodes.headers]
Authorization = "Bearer ${REPLYNODES_API_KEY}"
```

### Hermes

Configure the remote MCP server in Hermes with the endpoint and environment-backed header:

```yaml
mcp_servers:
  replynodes:
    url: https://mcp.replynodes.com/mcp
    headers:
      Authorization: "Bearer ${REPLYNODES_API_KEY}"
```



Do not paste a real key into configuration, source control, prompts, or logs. Do not infer package names or versions from this page. The REST API and remote MCP endpoint are the canonical integration surfaces; `GET /v1/capabilities` determines what is live.

## Quick links

- Claim flow: [`auth.md`](https://replynodes.com/auth.md)
- Integration workflow: [`quickstart.md`](https://replynodes.com/quickstart.md)
- Machine-readable summary: [`llms.txt`](https://replynodes.com/llms.txt)
- Live capabilities: [`https://api.replynodes.com/v1/capabilities`](https://api.replynodes.com/v1/capabilities)