API Reference

Every request to the Voidnet, exactly as the gateway processes them. This reference is generated from the gateway's source code, so it is always accurate.

Send a request

POST /v1-beta/mcp/{username}/{appname}

Proxy a JSON-RPC 2.0 request to a Void App's publisher server. The gateway authenticates, checks your purchase, enforces rate limits, then forwards the request.

Open POST /v1-beta/{adapter}/{username}/{appname}

MCP Streamable HTTP

Open an SSE stream

GET /v1-beta/mcp/{username}/{appname}

Open a Server-Sent Events stream for server-initiated messages from the publisher. Requires a valid Mcp-Session-Id from a prior initialize.

Open GET /v1-beta/{adapter}/{username}/{appname}

Terminate a session

DELETE /v1-beta/mcp/{username}/{appname}

Terminate an MCP session and closes the connection to the publisher. Requires a valid Mcp-Session-Id.

Open DELETE /v1-beta/{adapter}/{username}/{appname}

Operations

Health check

GET /health

Check the health status of the gateway and its dependencies (database, redis). Returns 200 only when all critical dependencies are reachable, 503 otherwise.

Open GET /health

Issue an OAuth access token

POST /oauth/token

Exchange a Voidnet API key for a short-lived JWT access token using the client_credentials grant.

Open POST /oauth/token

OAuth metadata

Authorization server metadata

GET /.well-known/oauth-authorization-server

OAuth authorization-server metadata per RFC 8414 — advertises the token endpoint, supported grant types, and JWKS URI.

Open GET /.well-known/oauth-authorization-server

Protected resource metadata

GET /.well-known/oauth-protected-resource

OAuth protected-resource metadata per RFC 9728 — advertises the authorization server and supported scopes.

Open GET /.well-known/oauth-protected-resource

JSON Web Key Set

GET /.well-known/jwks.json

The gateway's public signing keys as a JWKS. Clients use these to verify JWT access tokens issued by the gateway.

Open GET /.well-known/jwks.json