OpenAPI spec
The machine-readable OpenAPI 3.1 description of the amnt API. Import it into Postman, or generate a typed client.
Every endpoint, parameter and response shape as one OpenAPI 3.1 document — so you can generate a client instead of writing one.
https://www.amnt.io/api/v1/openapi.jsonNo key needed to read it. It is served from the same deploy as the API itself, so it can never describe endpoints that are not live.
Import it
- Postman — Import → Link → paste the URL. Set a collection variable
AMNT_API_KEYand every request is ready. - Insomnia / Bruno / Hoppscotch — the same URL, the same import menu.
- An AI coding tool — paste the URL and ask it to write the client. This is the most reliable way to get correct calling code on the first try.
Generate a typed client
# Types only - small, no runtime dependency.
npx openapi-typescript https://www.amnt.io/api/v1/openapi.json \
-o src/types/amnt.d.tspip install openapi-python-client
openapi-python-client generate \
--url https://www.amnt.io/api/v1/openapi.json# openapi-generator supports ~50 languages.
npx @openapitools/openapi-generator-cli generate \
-i https://www.amnt.io/api/v1/openapi.json \
-g go \
-o ./amnt-clientOne thing a generator cannot express
output is deliberately untyped: its shape depends on which connector the
agent runs on, and a creator can republish an agent on a different one.
Treat it as unknown and branch on what is present — see Output
shapes.
The MCP server is not in the spec
MCP speaks JSON-RPC over a single endpoint, which OpenAPI describes badly. Its contract is the MCP specification itself — see the MCP section.