// free tool
Define an API once. Generate agent tools everywhere.
Paste a cURL command or a JSON Schema. Get the same tool defined for OpenAI, Anthropic, MCP, Vercel AI SDK, LangChain and raw JSON Schema.
Runs entirely in your browser. Auth headers are read but never copied into the output — credentials belong in the environment, not a tool definition.
Questions
Which formats does it output?
OpenAI function tools, Anthropic tools, MCP (TypeScript with Zod), Vercel AI SDK, LangChain (Python), and plain JSON Schema. Define the endpoint once, take whichever you need.
Does it include my API key?
No — deliberately. It reads Authorization and X-API-Key headers so it can tell you auth is required, then leaves them out of the generated code, which reads from an environment variable instead. Baking a credential into a tool definition means it ends up in source control and in model context.
How are parameters inferred?
Query string keys become optional parameters, JSON body keys become required ones, and path segments that look like identifiers (numeric, UUID, or prefixed like cus_M4kd91) become required path parameters named after the preceding collection — /customers/cus_x becomes {customer_id}. Types come from the example values.
Why is the description a placeholder?
Because we can't invent an honest one from a cURL command. The description is the single highest-leverage field in a tool definition — it's what the model reads when deciding whether to call it. Write it yourself, then run it through our Tool Schema Linter.
Is anything sent to a server?
No. Parsing and generation run entirely in your browser. You can paste a cURL containing a real token and it never leaves the page.
// ready_when_you_are
Let's build your agentic advantage
Tell us what should be automated, connected or sold. We'll map the fastest path from idea to a production system.