List the tools the MCP server exposes
Returns the MCP server's tool list as a plain JSON array. Every entry is the same descriptor the MCP `tools/list` response carries, so the docs site and an MCP client see the same tools in the same order. The `subcategories` array pairs each top-level category with the distinct subcategory labels that fall under it, so a client can render the docs grouping without re-scanning `tools`.
Returns the MCP server's tool list as a plain JSON array. Every entry is the same descriptor the MCP tools/list response carries, so the docs site and an MCP client see the same tools in the same order. The subcategories array pairs each top-level category with the distinct subcategory labels that fall under it, so a client can render the docs grouping without re-scanning tools.
Response Body
application/json
application/json
curl -X GET "https://example.com/mcp/tools"{ "tools": [ { "name": "agent_list", "description": "List the agents the authenticated caller owns: each one's id, the name the owner gave it, its description, and the MCP client id it registered with. Takes no arguments, costs nothing, and reads the caller's own records only. `id` is opaque and never meaningful — quote it, do not parse it. `mcpClientId` is reported for attribution and is NOT a unique key, because two agents on one host may send the same `clientInfo.name`; key on `id`. A deleted agent is absent from this list, but its past spend still appears in `agent_usage` under the name it had, because a month-old charge belongs to the agent that made it. This tool does NOT run an agent and does NOT call a tool on an agent's behalf: a metered agent call spends the caller's credits, and that is a charge the run approval path exists to gate.", "category": "string", "subcategory": "string", "input": {}, "output": { "agents": [ { "id": "string", "name": "string", "description": "string", "mcpClientId": "string", "createdAt": "string", "updatedAt": "string" } ] } } ], "categories": [ "string" ], "subcategories": [ { "category": "string", "subcategories": [ "string" ] } ]}List your payment receipts GET
Returns the caller's own payment orders and their status, most recent first. This is a read-only viewer over what already exists: it never sends a transaction, never signs, and holds no key. Every query is owner-scoped, so another user's order can never appear here. A `txHash` is shown for the user to verify on a block explorer; putty does not broadcast it.
Read service metadata GET
Returns the identity of the running API: its name, the version of the HTTP contract, and the path of its OpenAPI document. Useful as a smoke test that the service is up and which build answered.