Use Cases · Agent Commerce by CertifiedData
Agent marketplace transactions
When one AI agent pays another for a deliverable, there is no trusted third party to mediate the handoff. Agent Commerce closes that gap: the signed receipt is simultaneously the settlement record and the proof that the paid artifact was the one delivered.
The agent-to-agent trust gap
In traditional marketplaces, platforms act as trusted intermediaries. In agent marketplaces, agents transact directly — often autonomously, without human review. That creates a trust problem on both sides:
Buyer agent
Needs proof the delivered artifact is the same one that was paid for and that the spend was governed by an approved policy.
Seller agent
Needs proof the payment actually executed through a policy-approved channel and that the receipt is independently verifiable — not just a claim in a database they do not control.
Agent Commerce solves both sides with one signed receipt that links the payment, the artifact hash, and the authorizing policy.
Example flow
Buyer agent hires a specialist
A buyer agent requests a logo, dataset slice, report, or other output from a specialist seller agent.
Policy evaluated before execution
Agent Commerce evaluates the spend against the active policy — spending limits, merchant allowlist, purpose tag. Blocked or over-limit requests never reach capture.
Seller agent returns the artifact
The specialist agent produces the output and computes its SHA-256 hash (artifact_hash). This hash is attached to the transaction with attachLinks() before capture.
capture() settles and issues signed receipt
The payment executes. A signed receipt is returned inline, containing receipt_id, transaction_id, artifact_hash, policy_id, sha256_hash, and ed25519_sig.
Buyer verifies independently
The buyer recomputes the artifact hash and checks it matches the artifact_hash in the receipt. Receipt validity is confirmed at GET /api/payments/verify/:receiptId — no account required.
What the receipt proves
One signed receipt, four simultaneous proof claims:
Financial record
amount, currency, rail, and captured payment event.
transaction_id · receipt_id
Provenance record
artifact_hash of the delivered output, linking payment to the exact artifact.
artifact_hash · certificate_id
Compliance record
policy_id and purpose_tag show the governing context that approved the spend.
policy_id · purpose_tag
Public verification target
Anyone can verify hashValid and signatureValid at /api/payments/verify/:receiptId.
sha256_hash · ed25519_sig
# Attach artifact hash before capture
cdp.transactions.attach_links(tx["transaction_id"], {
"artifact_hash": "sha256:3f4a9c2b…",
"decision_record_id": "dec_agent_logo_2026",
})
capture = cdp.transactions.capture(tx["transaction_id"])
receipt = capture["receipt"]
# receipt["artifact_hash"] == "sha256:3f4a9c2b…"
# receipt["ed25519_sig"] == "base64url:MEU…"
# receipt["policy_id"] == "pol_01jbm…"Build agent-to-agent transactions with built-in proof
Use sandbox to model marketplace workflows, then move to production with policy enforcement, signed receipts, and public verification surfaces built in.