The /mcp endpoint
Paseo runs a Model Context Protocol server at /mcp on https://api.augmentev.ai. It uses streamable HTTP. Any MCP client that supports streamable HTTP can start a session, list the tools and call them. The server names itself as:
| Field | Value |
|---|---|
server_info.name | paseo-gateway-mcp |
server_info.title | PASEO Gateway MCP |
| capabilities | tools |
Authentication
Every /mcp request needs a valid API key or an operator JWT. A request without one gets 401. Put the credential in the standard header:
initialize. Self-serve signup is paused. To get an API key, contact us.Connect a client
Point any streamable-HTTP MCP client at the endpoint. A bare initialize call over HTTP looks like this:
Most people won't write JSON-RPC by hand. Point your MCP client library at the URL and give it your credential. With a TypeScript MCP SDK, it looks roughly like this:
Tools
Each tool has a JSON Schema for its input and output. Each also has at least two examples in its MCP _meta.examples field. That lets a Code Mode client find and use the tools by itself. Live today:
| Tool | Does |
|---|---|
paseo.agent.list | Lists our agents. |
paseo.inference.generate | Generates text from one prompt, on a hosted open model. |
tier: confidential is refused.Calling a tool — paseo.agent.list
Idempotency & spend
You can safely retry a call. Send the same Idempotency-Key again and you get the saved answer back. MCP calls are not billed.
Discovery
A client can find /mcp without a credential. Two public files list the MCP URL:
- The agent card at
/.well-known/agent.json. The MCP URL is underinterfaces.mcp. - An OpenAI-style plugin manifest at
GET /.well-known/openai. The MCP URL is in theapis[]array, in the entry with"type": "mcp". It supportsETagandIf-None-Match.