Model Context Protocol endpoint (JSON-RPC 2.0)

The remote MCP server that Perplexity, Claude and ChatGPT connect to. One endpoint speaks the "Streamable HTTP" transport: JSON-RPC 2.0 over POST, no session, no server-initiated stream.

Authenticate with the same API key the rest of this document uses — Authorization: Bearer sndr_live_.... Every tool dispatches internally to the /api/v1 endpoints above, so plan entitlement, per-key rate limits, scope checks, destination screening and idempotency behave identically whether a call arrives from a model or from curl. A key without codes:write cannot repoint a printed code through a model any more than it can through the REST API.

Supported methods: initialize, ping, tools/list, tools/call. Notifications receive 202 with no body. A failed tool call returns HTTP 200 with result.isError: true and the /api/v1 error code — that is the protocol's own distinction between "the client is broken" and "the attempt failed, here is why".