amnt docs
DevelopersMCP server

What it is

Plug amnt agents into Claude, Cursor or any MCP client as callable tools. One URL, one key, paid from your credit balance.

POST https://www.amnt.io/api/mcp

MCP — the Model Context Protocol — is how an assistant like Claude discovers and calls tools. amnt runs an MCP server: point your client at it and the agents you choose show up as tools, with their inputs already described. When the assistant calls one, credits come out of your balance and the creator gets paid, exactly as if you had run it yourself.

What it looks like in practice
You:    Write shop copy for the walnut lamp, then make a picture of it.

Claude: [calls alice__product-description]  →  3 credits
        [calls studio__logo-mark]           →  12 credits

        Here is the copy and the image...

Why bother

🔌 No plumbingNo API client, no key per provider, no glue code. One config block
🎯 Specialists on tapAn agent someone tuned for one job usually beats a general model doing it from scratch
👀 Spend you can seeEvery tool description states its price in credits, so the assistant — and you — see the cost before it calls
🌍 Your agents everywherePublish once on amnt and it is available in every MCP client you use

How it works

Your client connects with your API key as a Bearer token.

It asks for the tool list. We return the agents that key is scoped to, capped at 25, each with a JSON Schema built from the agent's published fields.

When a tool is called we charge, run, refund on failure, pay the creator, and return the result as MCP content.

Same rails as everything else

The MCP server is a thin door onto the same runner the website and the REST API use. Same prices, same refunds, same balance, same rate limit — a tools/list counts as one request.

Protocol details

  • Transport: Streamable HTTP. One POST endpoint, JSON responses. No SSE — no amnt tool streams today.
  • Protocol version: 2025-06-18.
  • Methods: initialize, notifications/initialized, tools/list, tools/call. No resources or prompts yet.
  • Sessions: an Mcp-Session-Id is issued on initialize and echoed back, but no server-side state hangs off it — every request is authenticated by its key alone.
  • A plain GET on the endpoint returns server info, which some clients use as a liveness probe.

On this page