Three ways to connect. One catalog, one balance.

Pick whichever your agent speaks. Everything below works the same way under the hood.

AMXP is in private preview: the MCP server and HTTP API are live for video generation, keys are issued by hand, and the CLI comes next. Ask for a key at /start.

Skill

The fastest way. Paste this into your agent. It reads the skill, installs what it needs and asks you for a key.

MCP

Add the remote server to any MCP client. It exposes five tools: amxp_discover, amxp_inspect, amxp_execute, amxp_run (poll or stop) and amxp_balance.

mcp.json
{
  "mcpServers": {
    "amxp": {
      "url": "https://amxp.ai/mcp",
      "headers": { "Authorization": "Bearer $AMXP_API_KEY" }
    }
  }
}
Claude Code
claude mcp add --transport http amxp https://amxp.ai/mcp --header "Authorization: Bearer $AMXP_API_KEY"

CLI

For shell agents, scripts and CI. Not published yet; this is the interface it will have.

terminal
amxp discover -q "text to video"
amxp inspect kling-2.6-pro/text-to-video
amxp run kling-2.6-pro/text-to-video -i '{"prompt":"a fox in snow","generate_audio":false}' -w -o clip.json
amxp balance

HTTP API

Everything above is built on this. Authenticate with a bearer key. Base URL: https://amxp.ai/api/v1.

curl
curl https://amxp.ai/api/v1/discover \
  -H "Authorization: Bearer $AMXP_API_KEY" \
  -d '{"query":"text to video","limit":5}'

curl https://amxp.ai/api/v1/tools/kling-2.6-pro/text-to-video \
  -H "Authorization: Bearer $AMXP_API_KEY"

curl https://amxp.ai/api/v1/runs \
  -H "Authorization: Bearer $AMXP_API_KEY" \
  -d '{"tool":"kling-2.6-pro/text-to-video","input":{"prompt":"a fox in snow","generate_audio":false}}'

curl "https://amxp.ai/api/v1/runs/RUN_ID?wait=50" -H "Authorization: Bearer $AMXP_API_KEY"
curl https://amxp.ai/api/v1/balance -H "Authorization: Bearer $AMXP_API_KEY"

Also: GET /v1/runs, POST /v1/runs/:id/stop, GET /v1/whoami. Errors come back as { error: { code, message, details } }; a blocked run is a 402, a bad input a 400 or 422.

Concepts

Discover, inspect, execute

Discover searches the catalog in plain language and ranks endpoints by fit, price and health. Inspect returns an endpoint's input schema, price and typical run time. Execute reserves the price from your balance, runs the call and settles the exact cost.

Runs

Calls run asynchronously. A run moves from READY to RUNNING and ends in COMPLETED, FAILED, BLOCKED, STOPPED or TIMED_OUT. Poll it, or wait for it with a timeout.

Spend controls

Monthly budgets and per-run caps are enforced before a call runs. A call that would break one ends BLOCKED and costs nothing. See pricing.