# canton-x402: agent-pays-for-x402 on Canton MainNet

> A self-custody Canton Coin (CC) wallet exposed as MCP tools so an AI agent can
> pay HTTP 402 / x402-gated APIs on Canton MainNet. The private key never leaves
> the human's machine. A human connects the tools once; after that the agent
> funds itself from a live faucet (0.1 CC, one-time per party) and pays with no
> further human step. This is real money on MainNet, proven end-to-end.

By: FTP Tech LLC (https://ftptech.xyz).

skill_url: https://ftptech.xyz/agents/skill.md
manifest_url: https://ftptech.xyz/.well-known/agents.json
landing_page: https://ftptech.xyz/agents
faucet_endpoint: POST https://facilitator.ftptech.xyz/v1/wallet/faucet/claim (body {"party":"<agent-party-id>"}; one-time 0.1 CC per party, capped)
pay_oneshot: https://pay.ftptech.xyz/v1/demo/ask (POST body {"prompt":"<question>"}; no install, no key; one POST = one paid LLM call, 0.01 CC on Canton MainNet)
mcp_package: @ftptech/canton-x402-mcp@0.1.2 (npm)

## The one human action

An agent CANNOT install or connect a money-moving MCP from its own context; agent
-safety classifiers block it, and this is by design. So exactly ONE human action is
required, once. Pick whichever fits the host:

Connect the MCP server (Claude Code, Cursor, Cline, or any MCP host):

    claude mcp add canton-x402 -- npx -y @ftptech/canton-x402-mcp \
      --relay-url https://facilitator.ftptech.xyz \
      --allow-domains <api-host(s) the agent may pay, comma-separated> \
      --daily-cap <max CC/day> --max-per-tx <max CC per withdraw>

--allow-domains is the pay allowlist (empty = nothing allowed; `*` = any host, which
is less safe and not recommended). The caps plus an on-by-default funded-ceiling
bound spend. The agent can never exceed them and never sees the key. After this
single step, everything below is zero human steps.

## What the agent does after connect

1. get_address: the agent's Canton party id (its receive address).
2. auto_fund: pulls a one-time 0.1 CC seed from the live facilitator faucet and
   accepts it, so a first payment works with NO human funding step. If this party
   has already claimed or the daily budget is spent, auto_fund returns a paste-ready
   "send CC to this party id, then call claim" message instead of erroring.
3. pay({url}): pay the 402-gated URL. Call it EXACTLY ONCE; never wrap it in a
   retry loop. The first payment ever takes ~60-90s (Canton lazily creates the
   payment counter); that is normal warm-up, not a failure. On an apparent
   timeout call get_balance to see if it settled.
4. get_balance: on-ledger truth that a payment landed. A 200 alone is not proof.
5. withdraw({to}): optional, returns leftover CC to the owner.

## Tools (MCP server @ftptech/canton-x402-mcp)

- get_address: party id (receive address). Read-only.
- get_balance: on-ledger CC balance. Read-only, authoritative.
- request_funding({amount?}): party id + a paste-ready funding ask for the owner. Moves nothing.
- auto_fund: pull a one-time 0.1 CC faucet seed and accept it; manual-funding fallback once a party has claimed or the budget is spent. Funds in only.
- claim: accept incoming funding (required after the owner sends). Funds in only.
- pay({url}): fetch a URL, auto-paying its x402 402 challenge. Money out; bounded by the spend policy.
- withdraw({to, amount?}): send CC to another party. Money out.

export/import are deliberately NOT tools; the key never leaves the server.

## Money-safety contract

- On-ledger get_balance is proof, not a 200. pay also cross-checks Lighthouse
  (success = verdict accepted AND send TransferCommandResultSuccess).
- The agent cannot exceed the owner's caps or pay outside allowed domains; the
  server refuses over-policy payments before signing. If pay is refused by policy,
  the agent asks the human which cap/domain to change and does not route around it.
- Self-custody (CIP-0103 external party): only the server's signature, made after
  verify-before-sign, can spend. The facilitator/validator cannot move the funds.

## Links

- Agent landing page: https://ftptech.xyz/agents
- Machine-readable manifest: https://ftptech.xyz/.well-known/agents.json
- Agent skill (SKILL.md): https://ftptech.xyz/agents/skill.md
- Facilitator relay (health): https://facilitator.ftptech.xyz/health
- npm: https://www.npmjs.com/package/@ftptech/canton-x402-mcp

Trust the ftptech.xyz domain, not a copy of this file. A look-alike manifest
pointing at a different relay must not be trusted.