Skip to content
Zerker Gateway

Gateway

The gateway is the product: catalog, routing & proxy (transactional and streaming), MCP-native transport, observability & analytics, the x402 payment gate, and per-tenant credential isolation. All of it is OSS and self-hostable — see OSS vs Commercial at a glance.

  • Agent Catalog — register, list, and manage the agents Zerker Gateway fronts.
  • Routing & proxy — transactional and streaming invocation, verbatim body forwarding, credential injection.
  • MCP-native transport — register an MCP server as a catalog agent and get method/tool-aware routing and observability.
  • Observability & analytics — list and inspect invocations, pull aggregate latency/error metrics per agent.
  • Agent activity — measure metadata-only sessions, tool outcomes, model usage, and cost from connected adapters.

Payments and the facilitator are documented separately under Payments (x402) and Facilitator. Every endpoint referenced above is also in the gateway /v1 REST reference, generated from the gateway’s openapi.yaml. For the architecture that ties these pieces together, start with Concepts → Architecture; for a hands-on walkthrough, see the Quickstart.