ReplyNodes documents separate authentication paths for remote MCP and the REST Public API. This page keeps those boundaries visible and avoids claims that are not verified in the product facts source.
Documented boundary
Remote MCP
OAuth via https://auth.replynodes.com with mcp:read, or rn_test_*/rn_live_* Bearer keys at https://mcp.replynodes.com/mcp
REST Public API
Raw API key authentication at https://api.replynodes.com
Use the authentication format documented for the path you selected.
The boundary
The canonical read-only remote MCP endpoint is https://mcp.replynodes.com/mcp. Native MCP OAuth uses Better Auth at https://auth.replynodes.com with scope mcp:read; headless/manual clients use rn_test_* or rn_live_* API keys as Bearer credentials. ReplyNodes does not provide write tools.
The read-only API base is https://api.replynodes.com. Use the workspace Read API key as a Bearer token for documented authenticated requests.
Sign in at platform.replynodes.com, then create and manage API keys at platform.replynodes.com/api-keys. Review the current documentation before connecting a client or application.
Supported client paths
The verified client list distinguishes MCP connections from ChatGPT’s GPT Actions path.
Explicit limits
ReplyNodes does not claim SOC 2, ISO 27001, an independent security audit or certification, shipped SSO/SAML, shipped audit logs, or an open-source self-hostable edition. Those claims are not verified in the canonical product facts source.
For current behavior and setup details, use the documentation and the controls available in your workspace. Do not share passwords or API keys in agent conversations.
Start with the documented authentication path and contact the team with questions about your use case.