Integrates with Circle's CCTP for cross-chain USDC bridging, enabling merchants to receive payments on their chosen blockchain.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type @ followed by the MCP server name and your instructions, e.g., "@agent-commerce list my catalog"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Turn an AI agent into an Arcorapay merchant. Sell from a catalog, issue invoices in USDC, and get paid — payable cross‑chain (e.g. from Base, bridged to Arc via Circle CCTP). Ships as a one‑command CLI plus an MCP server any agent can run.
# one command: register a merchant wallet + write an MCP config
npx @arcora/agent-commerce onboard
# run the MCP server (your agent now has commerce tools)
npx @arcora/agent-commerce serveTestnet. This targets Arc Testnet via
https://arcorapay.xyz. Use testnet funds only.
Running serve exposes these MCP tools:
Tool | What it does |
| List the products this merchant sells (id, name, price). |
| Create an invoice for a catalog item → returns an invoice id + checkout URL. The buyer can pay in USDC on Arc or bridge from Base. |
| Look up an invoice's status: |
| Refund a paid invoice — returns the escrowed USDC to the original payer on Arc, within the 7‑day refund window. Registered only when a merchant signing key is available; funds cannot be redirected. |
The CLI mirrors these for humans/scripts: onboard, serve, refund <invoiceId>.
Related MCP server: InventPay MCP Server
Package | Published as | Role |
| Thin client for the Arcorapay public API (create invoice, status, webhooks). | |
|
| |
| MCP stdio server ( | |
| The one‑command CLI: |
The published @arcora/agent-commerce
inlines core + mcp + sdk, so installing it pulls only viem, siwe,
@modelcontextprotocol/sdk, and zod — no workspace deps.
By default a merchant is paid on Arc. To have revenue land on another chain, onboard with a payout chain (the relayer bridges Arc → your chain via CCTP):
npx @arcora/agent-commerce onboard --payout-chain 84532 --payout-address 0xYourAddresspnpm install
pnpm -r run build # builds @arcora/sdk + the CLI bundle
pnpm -r run test # core, mcp, cli unit tests (chain calls are mocked)Copy .env.example → .env and fill in your ARCORA_API_KEY (from onboard).
buyer ──pays USDC (Arc, or bridged from Base)──▶ Arcorapay escrow
│ │
│ agent calls create_invoice (MCP / SDK) │ settle
▼ ▼
your agent ◀── get_checkout_status ──────────── merchant payout (Arc, or
│ bridged to your chosen chain)
└── refund_invoice ──▶ returns escrow to the original payer (7‑day window)The merchant signing key is read‑only at runtime (ARCORA_MERCHANT_KEY env, or the
~/.arcora/merchant.key keyfile written by onboard). It is never logged and never
written into the MCP config.
refund_invoice can only return funds to the original payer of a paid invoice within
the on‑chain refund window — it cannot redirect funds to an arbitrary address.
Litepaper — English · Türkçe: what it is, how payments flow, why USDC/Arc/CCTP, the trust & security model.
Roadmap — English · Türkçe: what's done and what's next (mainnet, sponsored gas, more chains).
MIT
This server cannot be deployed
Multi-seller shopping for AI agents. Settle via Stripe MPP or x402 USDC on Base. Hosted.
Multi-seller shopping for AI agents. Settle via Stripe MPP or x402 USDC on Base. Hosted.
Agentic commerce network: discover sellers and products, negotiate, and pay USDC on Base via x402.
AI-agent product catalog: search, lookup & purchase routing over verified merchant data.
