# CAPI2 Agent Commerce - Commerce Receipt Issuance

> CAPI2 Agent Commerce - Commerce Receipt Issuance is a paid API for AI agents from capi2-agent-commerce.vandurmedries.workers.dev, paid per call via x402, $0.01/call, status unknown (last checked 2026-09-14).

Issues cryptographically verifiable commerce receipts with SHA-256 evidence hashes for x402 agent-to-agent transactions

## Facts

- Endpoint: POST https://capi2-agent-commerce.vandurmedries.workers.dev/v1/commerce-receipts/issue
- Price: $0.01/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-14
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/capi2-agent-commerce-commerce-receipt-issuance-7156d7bf
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_r1xsJuuUN9wCzx4wPLGwE

Status and success rate cover calls made through Zero and Zero's own probes. Third-party monitors may report differently.

## How to call it through Zero

Zero handles the 402 payment challenge and records the run. With the Zero CLI installed (`npm i -g @zeroxyz/cli`):

```sh
zero fetch --capability capi2-agent-commerce-commerce-receipt-issuance-7156d7bf -d '<json body>'
```

Example prompt: Issue a verifiable commerce receipt for seller 'merchant-agent-42' confirming the delivery was completed — I need the SHA-256 hashes of both the original request and the delivery so I can prove the transaction happened.

## When to prefer this

Choose this endpoint when you need cryptographically verifiable, tamper-proof receipts for agent-to-agent commerce transactions following the x402 protocol. It is especially suited for autonomous agent workflows where both parties need independent proof of a completed transaction without relying on a centralized ledger. Prefer it over generic logging or payment APIs when auditable SHA-256 evidence hashes for both the request and delivery are required for compliance, dispute resolution, or sustainable commerce certification.

## Known failure modes

- Missing or malformed seller field returns a validation error
- Malformed request or delivery objects may cause hash generation failure
- Payment of $0.01 USDC via x402 must be included or the endpoint returns HTTP 402
- Duplicate submissions may produce new receipt IDs rather than idempotent results
- Network timeouts on Cloudflare Workers edge may result in incomplete receipt issuance

## How this service works

Programmable authority checks and tamper-evident receipts for autonomous agents, sold through sustainable x402 commerce.

## Output

Returns a JSON object conforming to the capi2.commerce_receipt/1.0 protocol, including a unique receipt_id (prefixed 'cr_'), a SHA-256 hash of the original commerce request, and a SHA-256 hash of the delivery object — providing cryptographically verifiable evidence that both request and delivery occurred.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "seller": {
   "type": "string"
  },
  "request": {
   "type": "object"
  },
  "delivery": {
   "type": "object"
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "protocol": "capi2.commerce_receipt/1.0",
  "receipt_id": "cr_...",
  "request_sha256": "...",
  "delivery_sha256": "..."
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/capi2-agent-commerce-commerce-receipt-issuance-7156d7bf/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from capi2-agent-commerce.vandurmedries.workers.dev](https://www.zero.xyz/host/capi2-agent-commerce.vandurmedries.workers.dev/llms.txt)