Model Context Protocol endpoint (Streamable HTTP, stateless)
JSON-RPC 2.0 over Streamable HTTP. Send Content-Type: application/json and
Accept: application/json, text/event-stream, with your bearer in Authorization. Tools:
find_endpoints, inspect_endpoint, call_endpoint, account; resource nativeport://skill.
An empty balance still connects (reads work; call_endpoint returns the 402 as an error
result). Every other HTTP method answers 405 with Allow: POST. Client setup:
https://docs.nativeport.ai/mcp
Authentication
Your per-client bearer token — the API key the gateway issued to you. Present it in
Authorization: Bearer <token> form. A token that is missing, unknown, or revoked draws a
401. Before the call is sent upstream the token is removed (stripped, or swapped for the
upstream’s own credential); it never makes it past the gateway.
Request
A JSON-RPC 2.0 request or notification.
Response
The JSON-RPC response, as a JSON body or as a single text/event-stream event depending on the client’s protocol era.

