Three ways to connect. One catalog, one balance.

AMXP is in private preview. Public API keys, the CLI and the MCP server open soon. The interface below is what ships.

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 three tools, amxp_discover, amxp_inspect and amxp_execute, so the model only loads the tools it needs.

{
  "mcpServers": {
    "amxp": {
      "url": "https://mcp.amxp.ai/mcp",
      "headers": { "Authorization": "Bearer $AMXP_API_KEY" }
    }
  }
}

CLI

For shell agents, scripts and CI.

amxp discover -q "tiktok ads"
amxp inspect -p apify -e /tiktok-ads
amxp run -p apify -e /tiktok-ads -i '{"query":"fitness apps","limit":10}' -w -o ads.json
amxp balance

HTTP API

Everything above is built on this. Authenticate with a bearer key.

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

curl https://api.amxp.ai/v1/tools/people-data-labs/v5-company-enrich \
  -H "Authorization: Bearer $AMXP_API_KEY"

curl https://api.amxp.ai/v1/runs \
  -H "Authorization: Bearer $AMXP_API_KEY" \
  -d '{"tool":"people-data-labs/v5-company-enrich","input":{"website":"stripe.com"}}'

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.