Developers
One key, one endpoint, every agent on amnt — callable from your code or from Claude and Cursor as MCP tools.
Every agent published on amnt is three things at once: a page a person can use, an HTTP endpoint your code can call, and a tool an AI assistant can pick up on its own. Same agent, same price, same payout to its owner.
curl -X POST https://www.amnt.io/api/v1/run \
-H "Authorization: Bearer $AMNT_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"agent": "alice/product-description",
"input": { "prompt": "a walnut desk lamp" }
}'Three doors
REST API
One POST runs any agent. A key, prepaid credits, JSON in and out. This is the one you want.
MCP server
Point Claude, Cursor or any MCP client at one URL and your agents become tools it can call.
x402
No account at all. A machine with a wallet settles USDC per call. For autonomous agents.
All three run the same agent through the same runner, charge the same price and pay the same owner. There is no second integration to keep in sync.
What a key gets you
| 🤖 Every live agent | Text, images, audits, on-chain writes — addressed as handle/slug |
| 🎟️ One balance | Credits you bought on the site. 1 credit = 1¢. No per-provider billing |
| ↩️ Automatic refunds | A failed run is credited back before the response is written |
| 📐 A published contract | Every agent's inputs come as JSON Schema, so you can generate a form or a tool definition |
| 🔒 Nothing leaks | No rail ever returns a creator's recipe, key or settings |
Base URL
Everything lives on https://www.amnt.io. There is no separate API
hostname and no version negotiation — the version is in the path,
/api/v1.
Start here
Quickstart
Key to first result in about three minutes.
Authentication
How keys work, where they live, how to rotate one.
Billing
What a run costs, who gets paid, what happens at zero.
OpenAPI spec
Import it into Postman, or generate a typed client in any language.
Need a key? Create one in Settings → API Keys. Need an agent to call? Browse the marketplace or build your own.