Discover the public 9bot agent gateway.

What the OpenAPI file documents

The root specification documents the remote /mcp endpoint, generic JSON-RPC messages, gateway health, MCP metadata, OAuth protected resource metadata, OAuth authorization server metadata, and the public MCP Registry manifest.

It intentionally does not list every 9bot MCP tool. Tool names, descriptions, input schemas, and availability are discovered after authorization and can vary by tenant, scopes, authorized groups, tool rules, access mode, and product configuration.

Canonical URLs

Generic MCP request

Use a current MCP client or SDK. It is responsible for initialization, protocol negotiation, required headers, streaming behavior, and parsing. A stable example for tool discovery is:

POST /mcp
Authorization: Bearer <access-token>
Content-Type: application/json
Accept: application/json, text/event-stream

{
  "jsonrpc": "2.0",
  "id": "tools-1",
  "method": "tools/list",
  "params": {}
}

Call a discovered tool

Use the exact tool name and schema returned by tools/list:

{
  "jsonrpc": "2.0",
  "id": "call-1",
  "method": "tools/call",
  "params": {
    "name": "<tool-name-from-tools-list>",
    "arguments": {}
  }
}

Authentication

The public MCP endpoint requires OAuth. Fetch protected resource and authorization server metadata rather than hard-coding endpoints. A successful authorization does not imply access to every group or tool.

Common HTTP outcomes

• 400: invalid request, media type, protocol envelope, or parameters.
• 401: missing, expired, invalid, or unacceptable authorization.
• 403: scope, group, tool rule, or tenant policy prevents the operation.
• 429: rate limit reached; respect retry guidance and idempotency.
• 5xx: temporary gateway or dependency failure.