One backend. Multiple agent-commerce protocols. Self-hosted and non-custodial.
DOCKER_UID=$(id -u) DOCKER_GID=$(id -g) before
docker compose up. This keeps the generated deployment manifest
host-writable. Docker Desktop does not need this.
The disposable local stack includes Anvil, MockUSDC, a demo merchant API, the
gateway and a dashboard.
To stop and wipe state: `docker compose down -v`.
### `agent-commerce demo`
From a repository clone, one command starts the stack and runs the buyer agent:
```bash
npm run agent-commerce -- demo
```
It starts the stack with `docker compose up --build --detach --wait`, which
returns once every service with a health check is healthy, then runs
`npm run demo:agent`. A failing step stops the run with exit code 1, after
printing the end of its error output and the command to rerun it by hand.
`demo` does not run `doctor`. The Linux note above applies, and the stack
keeps running in the background until `docker compose down -v`.
## How it works
```text
┌──────────────────────────────────────────────────────────────────────────────┐
│ AI Agent │
└───────────────────────────────────────┬──────────────────────────────────────┘
│ MCP · A2A · ACP · HTTP
│ payment proof
│ Agent-Authorization
┌───────────────────────────────────────▼──────────────────────────────────────┐
│ Agent Commerce Gateway (yours) │
│ │
│ protocol adapters → ExecutionPipeline │
│ │ │
│ ┌────────────────────┬──────────────┴──┬────────────────┐ │
│ ▼ ▼ ▼ ▼ │
│ AuthorizationProvider PaymentProvider BackendExecutor ReceiptStore │
│ (ap2) (x402, mpp) (bounded HTTP) (SQLite) │
└───────────────────────────────────────┬──────────────────────────────────────┘
│
┌──────────▼─────────┐
│ Your backend API │
└────────────────────┘
```
Every protocol adapter uses one execution pipeline, so payment enforcement does
not depend on the adapter. See [Architecture](docs/architecture.md).
## Configure a resource
```yaml
resources:
market_report:
name: Premium Market Report
backend:
type: http
method: GET
url: ${MERCHANT_API_BASE_URL}/api/report
timeoutMs: 10000
pricing:
type: fixed
amount: "0.01"
currency: USDC
expose: [http, mcp]
payments: [x402]
```
The gateway calls your existing backend, which needs no SDK or changes.
```bash
npm run agent-commerce -- init # generate a config interactively
npm run agent-commerce -- validate # fails loudly, exits non-zero
```
Already have an OpenAPI description? Generate the resources from it
(**experimental**):
```bash
agent-commerce import openapi ./openapi.yaml
```
It writes a reviewable `resources:` fragment with path, query and JSON body
bindings and supported schemas. The source document never decides price or
exposure: `pricing` appears only with `--free` and `expose` only with
`--expose`, and credentials are never imported. See
[OpenAPI import](docs/openapi-import.md) for the supported subset.
See [docs/configuration.md](docs/configuration.md).
## Protocol support
| Protocol | Status | Pinned revision |
| ------------ | ------------ | ------------------------------------------------------------------------------------------------------------ |
| **HTTP** | Supported | native routes |
| **MCP** | Supported | `2026-07-28` and `2025-11-25`, `@modelcontextprotocol/server@2.3.0` |
| **x402** | Supported | x402 v2 (`@x402/core`, `@x402/evm`, `@x402/svm`, `@x402/near`), scheme `exact`, EVM and Solana; NEAR partial |
| **MPP** | Experimental | `mppx@0.13.1`, `charge` + `evm` + EIP-3009, USDC on Base Sepolia and Base |
| **A2A** | Experimental | A2A v1.0.1, binding `JSONRPC`, method `SendMessage`, x402 extension |
| **ACP** | Experimental | ACP `2026-04-17`, REST checkout + discovery |
| **AP2** | Experimental | AP2 `v0.2.0`, Direct Checkout Mandate verification |
| **ERC-8409** | Experimental | draft `SergeevDmitry/ERCs@0ee33230`: signed quotes on x402 EVM offers |
| UCP | Planned | no implementation |
[AP2](docs/protocols/ap2.md) is an authorization method, not a transport. It verifies a
mandate before a paid resource settles; the gateway does not issue the mandate
or its Checkout Receipt.
The experimental entries above ship off by default with documented subsets:
[A2A](docs/protocols/a2a.md), [ACP](docs/protocols/acp.md),
[AP2](docs/protocols/ap2.md#not-implemented), [MPP](docs/protocols/mpp.md) and
[ERC-8409 quotes](docs/protocols/x402.md#erc-8409-signed-quotes). Supported
[MCP](docs/protocols/mcp.md) and [x402](docs/protocols/x402.md) are also scoped.
ACP exposes only its five checkout operations; merchant `payment_data` is never
converted into a gateway payment proof.
`GET /.well-known/agent-commerce` reports `supportedSpec`, `capabilities` and
`unsupported` for registered adapters and providers. `agent-commerce doctor`
prints the `unsupported` lists for A2A, ACP and AP2 when they are enabled.
### Versioning
Minor releases may break experimental configurations, integrations or types.
This applies to MPP, A2A, ACP, AP2, ERC-8409 quotes and
`agent-commerce import openapi`.
Runtime adapters and providers report `status: experimental` in
`GET /.well-known/agent-commerce`. Pin an exact version and test upgrades
before deploying them. Since 2.1, some supported x402 behavior and types
differ from 2.0; see [Upgrading from 2.0 to 2.x](docs/migration-2.1.md).
## Payment model
- **Non-custodial.** Buyer payments go directly to the merchant address in
`payTo` (`recipient` for MPP). The gateway does not require buyer or merchant
private keys. Local facilitator mode uses a separate key to pay gas.
Experimental ERC-8409 quotes use a dedicated, unfunded signing key.
- **Fail closed.** Missing, malformed, expired, replayed, wrong-amount,
wrong-recipient, wrong-network and wrong-asset payments are rejected.
- **Replay-safe twice over.** The EIP-3009 or Permit2 nonce stops a double
spend on-chain; the gateway additionally reserves a `replayKey` derived from
the authorization before it settles anything.
- **On-chain settlement in CI.** The end-to-end test asserts the buyer's balance
falls and the merchant's rises by exactly the price, with a real transaction
hash in the receipt. A log line saying "payment successful" would not count.
- **One selected rail per resource.** A resource can name several rails, such as
`payments: [x402, mpp]`; the first enabled one serves it, and nothing selects
or falls back between rails per request.
- **Authorization is separate from payment.** A resource can also require an
AP2 mandate, verified before settlement and spendable exactly once. It never
moves money and never unlocks a resource on its own - the payment still has
to be real.
## Public networks
Public networks use the same execution pipeline with a remote facilitator.
Choose the network in config; Base mainnet also requires `allowMainnet: true`.
### It has actually settled
These transactions each moved 0.01 USDC from a buyer to a merchant through a
remote facilitator:
| Rail | Network | Method | Transaction |
| ---- | ------------- | ---------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------- |
| x402 | Base Sepolia | EIP-3009 | [`0xea41b234c4…`](https://sepolia.basescan.org/tx/0xea41b234c4645a4d335589ec9753646aa7cccd1b97e9e15823b88bff7b54a247) |
| x402 | Base Sepolia | Permit2 | [`0xa66f56cf39…`](https://sepolia.basescan.org/tx/0xa66f56cf39daeae958b5067c99383da4974c2ae6450786c0f9088700fa6439fe) |
| x402 | Base | EIP-3009 | [`0x57ec81c2a3…`](https://basescan.org/tx/0x57ec81c2a360d14d59a43cf4e24be09a6bd75cbe6185016372895bda73e42763) |
| x402 | Base | Permit2 | [`0x79d3da1145…`](https://basescan.org/tx/0x79d3da114522d4b056b29fad34d6492ce5662b92efd8ef2fd1ac21295ab71a42) |
| x402 | Solana Devnet | SPL transfer | [`5289xbeyHJ…`](https://explorer.solana.com/tx/5289xbeyHJPX1vX9DsLwGGJaGJJCH45qUtArhoTyxdgmWbXqZSjVPuJ3jyyLG4VrT9mFTCkLKhcoNfb1tuJ5qheb?cluster=devnet) |
| x402 | Solana | SPL transfer | [`E7gAuG8pMA…`](https://explorer.solana.com/tx/E7gAuG8pMArQjgRvGCwqm6S4qpt4xFNuhUTxeaZ5M1M1z1VA8eybyJJAXyo9paecCKnyrxYEuppoAemhntnnzTa) |
| x402 | NEAR Testnet | NEP-141 transfer | [`5tdtGLv4TB…`](https://testnet.nearblocks.io/txns/5tdtGLv4TBifK7c12hEdRuvxvNNrWjcWDH4e1ApUcE1W) |
| x402 | NEAR | NEP-141 transfer | [`7hU3imHepV…`](https://nearblocks.io/txns/7hU3imHepVZazGv53QfWYMGnWX5sVFxJAepemmwVSzt2) |
| MPP | Base Sepolia | EIP-3009 | [`0x5d9fcd111b…`](https://sepolia.basescan.org/tx/0x5d9fcd111b615bb8fc9e56d55096f119fc81c3c72c334f813cfaecee402d0ac3) |
| MPP | Base | EIP-3009 | [`0xf4255bd7ec…`](https://basescan.org/tx/0xf4255bd7ec46ed06505dedfb5f9537924bd2633816e7952ec6f2b468395b1087) |
Facilitators broadcast these payments and paid their ETH, SOL or NEAR fees.
Permit2 requires an initial, gas-paying token approval from the buyer. The
NEAR runs used the suite's SDK facilitator and relayer; support remains
partial pending hosted-facilitator settlement. Buyer and merchant keys stayed
outside the gateway. The smoke suites verified settlement on-chain.
Reproduce with `npm run test:testnet`, which spends test USDC, or
`npm run test:mainnet`, which spends real USDC. Both run only by hand; see
[Base mainnet](#base-mainnet) and [smoke tests](docs/smoke-tests.md). The
suites also cover NEAR testnet and mainnet (settled) and Arbitrum Sepolia (not
yet run).
### The facilitator model
A **facilitator** verifies the buyer's authorization and broadcasts the
transfer. It is the only component that needs gas.
| `facilitator.mode` | Who signs | Where it is allowed |
| ------------------ | -------------------------------------- | ------------------------------------------------------------------ |
| `local` | this process, with a key you configure | a local Anvil chain; refused on mainnet, fails readiness elsewhere |
| `remote` | an HTTP facilitator you point at | anywhere |
With `remote`, the gateway holds no facilitator signing key. The buyer signs an
EIP-3009 authorization without ETH, and the facilitator pays gas. Because the
authorization fixes the recipient, amount and chain, the facilitator cannot
redirect the transfer. It can see authorizations and refuse service.
Remote facilitator auth supports `none`, `bearer` and `cdp`. `cdp` loads the
optional peer `@coinbase/x402`, which signs a fresh JWT per request; bearer auth
needs no extra peer. Other types are rejected at config load.
### Base Sepolia
```yaml
payments:
x402:
enabled: true
network: eip155:84532
rpcUrl: https://base-sepolia-rpc.publicnode.com # health checks only
asset: "0x036CbD53842c5426634e7929541eC2318f3dCF7e" # Circle USDC
assetName: USDC
assetVersion: "2"
assetDecimals: 6
payTo: ${MERCHANT_WALLET}
maxTimeoutSeconds: 300
facilitator:
mode: remote
url: https://x402.org/facilitator
auth: { type: none }
```
Full config in [`examples/base-sepolia/`](examples/base-sepolia/). Test USDC
from [faucet.circle.com](https://faucet.circle.com); the buyer needs no ETH.
`npm run test:testnet` drives the whole flow and reads the result back off the
chain.
The local dev chain is `eip155:31337`, Anvil's default chain id, so the network
says whether a deployment is local, testnet or mainnet. `doctor`, `health()`
and `/.well-known` report it.
### Base mainnet
Mainnet moves real funds. Config validation requires:
| Required | |
| -------------------------------------------------------------- | -------------------------------------------------------------- |
| `allowMainnet: true` | mainnet is never a default |
| `facilitator.mode: remote` | `local` needs a funded gas key inside this process |
| an HTTPS `facilitator.url` | |
| `allowUnauthenticatedFacilitator: true` | required when `facilitator.auth.type` is `none` |
| a non-development destination (`payTo` or `recipient`) | |
| Base USDC with `assetName: "USD Coin"` and `assetVersion: "2"` | the buyer signs this EIP-712 domain; `"USDC"` is wrong on Base |
Full config in [`examples/base-mainnet/`](examples/base-mainnet/), and
[`examples/base-mainnet-payai/`](examples/base-mainnet-payai/) for an
unauthenticated facilitator. The mainnet smoke suites cover x402 and MPP and
spend real USDC when their opt-ins and credentials are present.
`agent-commerce validate` reports any of the above before anything starts, and
`doctor` prints `LIVE MAINNET MODE - REAL FUNDS`.
> The public-network suites never run in CI, because a workflow would need a
> funded buyer key in repository secrets. Run them from the machine that holds
> the wallet. A test whose required settings are missing skips itself.
## Diagnostics
```console
$ npm run agent-commerce -- doctor --config config-demo.yaml
PASS Config valid: 2 resource(s), merchant "Demo Data Store" (using local chain manifest .deploy/local.json for X402_ASSET, X402_ASSET_NAME, X402_ASSET_VERSION, X402_ASSET_DECIMALS, MERCHANT_WALLET, X402_FACILITATOR_PRIVATE_KEY)
PASS Gateway healthy and ready at http://127.0.0.1:8080
PASS Backend 2/2 backend host(s) reachable
PASS Protocols http=on mcp=on (/mcp) a2a=off acp=off
INFO A2A disabled
INFO ACP disabled
INFO AP2 disabled
PASS Payments x402 v2 (scheme=exact) enabled - LOCAL dev chain (eip155:31337), destination=0x7099…79C8, facilitator=local (in-process), paymentFlow=authorization
INFO Payments (MPP) MPP not configured
PASS Storage sqlite schema v3 writable; receipts=2
PASS Protocol versions reported by gateway /.well-known/agent-commerce
Score: 7/7 checks passed
```
`doctor` compares live settlement terms with local config for each rail and
resource: offer order, network, token, payee and transfer method, plus decimals
and payment flows when published. Mismatches fail the check. It also names
failing offers when health is published; reasons appear in gateway debug logs.
Exits non-zero if anything fails. `--json` for machines.
### `agent-commerce version`
```bash
npm run agent-commerce -- version
```
Prints the CLI version and, for each protocol SDK and runtime library, the
version the package declares and the area that uses it. These are the pins in
`package.json`, optional peers included, not the versions installed in
`node_modules`. `agent-commerce --version` prints the CLI version alone.
## Exposure and access
The demo binds everything to `127.0.0.1`. Before putting the gateway anywhere
reachable by anyone else, know the split:
- **Agent routes** (`/api/resources/:id/invoke`, `/mcp`, the A2A mount) are
unauthenticated by design - paid resources are protected by payment, not by a
password. ACP is the exception: its checkout routes require a bearer token.
- **Operator routes** (`/api/receipts`, `/api/events`, `/api/payment-attempts`)
expose the merchant's commerce ledger: payer addresses, amounts and settlement
hashes. They require `server.adminToken` and return **404** if none is configured.
- **Browsers** are governed by `server.allowedOrigins`, an explicit allowlist
that defaults to empty.
- **There is no rate limiting.** A free resource is an unauthenticated proxy to
your backend at whatever rate a caller chooses. Quotas and abuse controls
belong in your API or your edge.
[SECURITY.md](SECURITY.md) states plainly what this does and does not protect.
## Development
```bash
npm run verify # contract + lint + typecheck + test
npm run test:e2e # deterministic end-to-end, boots its own chain
```
Foundry (`anvil`, `forge`, `cast`) is needed for the chain work.
See [CONTRIBUTING.md](CONTRIBUTING.md).
## Roadmap
**Now** - MCP, x402 v2, settlement on the local chain, Base Sepolia, Base
mainnet, Solana devnet and Solana mainnet, receipts, doctor, deterministic
demo, experimental A2A v1.0.1 and ACP `2026-04-17` checkout adapters,
experimental AP2 v0.2.0 mandate verification, experimental MPP `charge`
payments, and experimental OpenAPI import.
**Next** - a `doctor` GitHub Action · UCP ·
autonomous-mode AP2 (open mandates, agent key binding, constraint evaluation) ·
more of ACP (carts, feed, delegated payment) · Shopify and WooCommerce examples ·
PostgreSQL · richer observability · multi-file and remote OpenAPI sources.
New protocols need evidence that the adapter model works in real use before
they are added to a release.
## Documentation
| | |
| ---------------------------------------------- | ------------------------------------------- |
| [Architecture](docs/architecture.md) | how the pieces fit |
| [Payment flow](docs/payment-flow.md) | the paid round trip and failure paths |
| [Protocols](docs/protocols.md) | supported and unsupported protocol features |
| [AP2](docs/protocols/ap2.md) | mandate verification and the trust model |
| [Configuration](docs/configuration.md) | `config.yaml` reference |
| [Upgrading from 2.0](docs/migration-2.1.md) | changes that can break a 2.0 setup |
| [Smoke tests](docs/smoke-tests.md) | settling on public networks, by hand |
| [OpenAPI import](docs/openapi-import.md) | generate resources from an existing API |
| [Security model](docs/security.md) | trust boundaries, and what we do not defend |
| [Contracts](docs/contracts.md) | the frozen cross-area contract |
| [Adapter guide](docs/contributing-adapters.md) | add a protocol or a payment rail |
## License
[Apache-2.0](LICENSE).