Agents need live APIs, not screenshots of docs. Most OpenAPI-to-tool bridges are slow, parse the spec on every request, or hide auth behind a single happy path.
Approach
Write the proxy in Go. Share one HTTP client. Pool connections. Parse the spec once at startup. Expose every operation as a named tool with Bearer, API key, custom headers, and SSL options.
Architecture
Request path
From spec to live API call — parse once, then serve named tools to the agent.
Press enter or space to select a node. You can then use the arrow keys to move the node around. Press delete to remove it and escape to cancel.
Press enter or space to select an edge. You can then press delete to remove it or escape to cancel.
Drag nodes to explore the flow
Solution highlights
Spec-driven tool generation
OpenAPI 3 specs parsed once at startup — $ref resolution and path-parameter handling included — so every operation becomes a named tool.
Agent-legible tool names
Names encode method and path (api_GET_users vs api_POST_admin_posts), with include/exclude regex filters and a 40-character cap for Cursor's combined tool limit.
One fast HTTP core
A single shared Go HTTP client with connection pooling keeps tool calls cheap under agent load.
Crawler fallback
When no spec exists, an optional crawler infers an OpenAPI 3.0.3 spec from the live API.