Skip to content

Agent-native marketplace

The marketplace your AI agents can shop in.

Give an agent its own key and a budget. It discovers tools over MCP or REST, buys within the rules you set, pays in USDC and installs what it needs — while you stay in control of every limit.

How it works

Autonomous buying, with a human holding the purse strings

  1. 01

    You create a key

    In your workspace, create a key for each agent and set its budget, auto-approve ceiling and allowed listing types.

  2. 02

    Your agent connects

    Add the AgentLoomX MCP server to any MCP client, or call the REST API. Discovery needs no key at all.

  3. 03

    Rules decide

    Each purchase is checked against your rules: approved instantly, sent to you for a decision, or refused.

  4. 04

    It pays and installs

    Paid items settle in USDC on Base, verified on-chain. The agent downloads the package with its key.

Spending rules

Guardrails your agents can't talk their way around

Rules are enforced on our side, not in the agent's prompt. An agent can explain why it wants something — but only your settings decide whether money moves.

  • Hard spending limitsPer-purchase, daily and monthly caps the agent can never exceed.
  • Approval ceilingAnything above your auto-approve amount waits for you — with the agent's stated reason.
  • Scoped accessLimit an agent to agents, skills or plugins, or to specific categories.
  • Pause or revoke instantlyEvery key can be paused or revoked from your workspace in one click.
  • Exact-amount paymentsEach payment has a unique amount and is verified on-chain before access is granted.
  • Full activity logSee every request, decision and purchase your agents make.

Connect

Two lines of config. Seven tools.

The MCP server exposes search_catalog, get_listing, get_my_agent, request_purchase, check_purchase, list_purchases and get_library. Everything is also available as plain REST.

mcp.json — Claude, Cursor, OpenClaw & other MCP clients
{
  "mcpServers": {
    "agentloomx": {
      "type": "http",
      "url": "https://agentloomx.com/api/mcp",
      "headers": { "Authorization": "Bearer alx_agent_YOUR_KEY" }
    }
  }
}
REST — any language
# 1. Search (no key needed)
curl "https://agentloomx.com/api/v1/catalog?q=browser&agent_ready=true"

# 2. Ask to buy — your owner's rules decide
curl -X POST https://agentloomx.com/api/v1/agent/purchases \
  -H "Authorization: Bearer alx_agent_YOUR_KEY" \
  -H "Content-Type: application/json" \
  -d '{"listing":"browser-ops-pro","reason":"Need headless browser automation for the QA task"}'

# 3. If payment is due: send the exact USDC amount, then
curl -X POST https://agentloomx.com/api/v1/agent/purchases/REQUEST_ID/verify \
  -H "Authorization: Bearer alx_agent_YOUR_KEY" -d '{"tx_hash":"0x…"}'

Agent-ready

Tools your agent can install today

Listings with a downloadable package or a machine interface, so agents can acquire and use them without a human in the loop.

Browse everything

Payments

Settled in USDC, verified on-chain

Prices are in US dollars and paid in USDC on Base. Every payment request has a unique amount, so a transfer can only ever settle the purchase it was meant for. Access is granted the moment the transfer confirms.

Does my agent need its own crypto wallet?

Only for paid listings. Free listings need nothing but a key. For paid ones, the agent (or you) sends USDC from any wallet on Base — the payment request tells it exactly what to send.

Can an agent overspend?

No. Per-purchase, daily and monthly limits are enforced server-side, and requests above your auto-approve ceiling wait for your decision.

Who owns what an agent buys?

You do. Purchases land in your workspace library, and your agent can download them with its key.

Can I use this without crypto?

Yes — free listings work today, and you can always browse and buy from your own account on the website.