Agent Commerce live demo
Pick a sample transaction, click Authorize & execute, and get back a signed authorization plus an Ed25519-signed receipt. Same policy engine, same signing key, same canonical payload as production. Nothing is persisted.
- Policy engine evaluates amount, merchant, and purpose before money moves
- Ed25519-signed authorization record for every allowed or blocked decision
- Ed25519-signed receipt with SHA-256 hash and canonical payload (RFC 8785)
- Verifiable outside our system against the published public signing key
Sample transactions
Most realistic · edit the payload freely
Transaction payload
Demo policy caps: max $5,000 · currencies usd/eur/gbp · merchants dataset-marketplace, model-registry, infra-api, training-data-coop · purposes training-data, inference-data, compute, api-call, model-license. Anything outside these bounds is blocked (and the block is signed too).
Signed output
Pick a sample or edit the payload, then click Authorize & execute.
How the flow works
The demo runs the same three-phase pattern as production — only the rail and persistence are stubbed. Every phase produces a tamper-evident artifact.
Authorize
Policy rules (spend cap, allowed merchants, allowed purposes) are evaluated. Every outcome — allowed or blocked — produces a signed authorization record.
Execute
Approved authorizations dispatch to the configured rail (Stripe, USDC on Base/Ethereum, ETH). Sandbox uses a simulated rail so demos never move real money.
Issue receipt
On completion, an Ed25519-signed receipt is emitted with a canonical payload, SHA-256 hash, and a permanent public verification URL.
Prefer code?
Open-source SDK, MCP server, examples
The Agent Commerce client, MCP server, and integration examples are MIT-licensed. Clone it, wire up a sandbox key, run the same flow from your terminal.
git clone https://github.com/certifieddata/certifieddata-agent-commerce-public cd certifieddata-agent-commerce-public npm install && npm run example
Where teams use this
Anywhere an autonomous agent moves money and someone has to answer for it later.
Procurement →
Give agents controlled purchasing with spend limits, approval routing, and signed receipts per purchase.
API payments →
Let software agents pay for external APIs with policy enforcement and audit-ready logs on each call.
SaaS renewals →
Automate recurring spend decisions with explicit policy boundaries and traceable outcomes.
Dataset & digital asset purchases →
Connect AI-triggered purchases to verifiable financial records and certified artifact provenance.
For compliance, audit, and legal review
Evidence an auditor can verify
EU AI Act · Article 12
Record-keeping
Signed receipts and authorization records give regulators an immutable evidence chain for every AI-initiated transaction.
EU AI Act · Article 13
Transparency to deployers
Machine-readable policy decisions and rationales document why a transaction was allowed or blocked.
EU AI Act · Article 50
Transparency obligations
Every receipt is publicly verifiable by the counterparty using CertifiedData's published Ed25519 public key.
From sandbox to production
Start here. Move up when you're ready — the signing, policy, and receipt schemas stay identical.
Sandbox
No credit card$0
- •Unlimited demo runs (rate-limited)
- •Real Ed25519 signatures
- •No persistence
You're here
Free account
Real API key$0
- •Sandbox API key (cdp_test_)
- •Receipt persistence
- •Public verification URLs
Verify it yourself
Every surface here is a live public endpoint — no account, no API key.
Try the other pillars
Three pillars, one proof system. Each runs anonymously, each produces real signatures.
Frequently asked
Are the signatures real or simulated?+
Real. Every demo produces an Ed25519 signature over an RFC 8785 canonical payload using the same signing key as production sandbox authorizations. You can verify outside our system using the public key at /.well-known/signing-keys.json.
Does the demo move real money?+
No. The demo never touches Stripe, a card, or a chain. It exercises the policy engine and the signing layer end-to-end; the 'rail' field in the receipt is set to sandbox.
What happens when a transaction is blocked?+
The policy engine still produces a signed record of the block — the authorization payload records the violations, the rationale, and the policy decision. Blocked events are audit evidence too.
What are the anonymous rate limits?+
30 demo requests per minute per IP. If you need unlimited test runs, a free account issues a sandbox API key (prefix cdp_test_) with full receipt persistence.
How is this different from /sandbox?+
The sandbox is the developer landing — ephemeral API keys plus curl examples for the real production endpoints. This page is the interactive proof-of-concept: one click produces the full signed evidence chain, no key management required.
What schema do the receipts follow?+
payment_receipt.v1 — a canonical, versioned schema documented at /agent-commerce/docs/schema-registry. Demo receipts use the suffix _demo so they can't be confused with production receipts.
Keep your signed receipts
Free account · no credit card · sandbox API key · receipt persistence.