# Cross-Protocol Receipt

> Cross-Protocol Receipt is a paid API for AI agents from phion.systems, paid per call via x402, $0.004/call, status unknown (last checked 2026-10-12).

Bundles protocol receipt commitments across multiple protocols into a single auditable, consistent receipt artifact

## Facts

- Endpoint: POST https://phion.systems/v1/paid/trust/cross-protocol-receipt?utm_source=zero.xyz
- Price: $0.004/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-12
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/cross-protocol-receipt-0642e574
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_Uk1NH5ySr1gSXE-zr9osz

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 cross-protocol-receipt-0642e574 -d '<json body>'
```

Example prompt: Take the payment and interaction receipts from this multi-protocol agent session and bind them into a single auditable cross-protocol receipt bundle I can use for compliance records.

## When to prefer this

Use this endpoint when an agent workflow spans multiple protocols (e.g. x402 payments, A2A handoffs, MCP interactions) and you need a single, authoritative, tamper-evident receipt that captures all protocol-level commitments in one auditable artifact — especially for compliance, dispute resolution, or portable record-keeping across agent systems.

## Known failure modes

- Missing or malformed input receipt data returns a validation error
- Incompatible protocol receipt formats may cause binding failure
- Incomplete commitment data results in a partial or rejected bundle
- Service unavailability returns a 402 or 5xx error

## How this service works

Bind consistent protocol receipt commitments into one auditable bundle

## Output

A signed, auditable bundle that binds together protocol receipt commitments from multiple protocols into a single consistent artifact, suitable for compliance review, dispute resolution, or portable record-keeping.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "$schema": "https://json-schema.org/draft/2020-12/schema",
 "required": [
  "input",
  "output"
 ],
 "properties": {
  "input": {
   "type": "object",
   "required": [
    "body"
   ],
   "properties": {
    "body": {
     "type": "object",
     "additionalProperties": true
    }
   }
  },
  "output": {
   "type": "object",
   "required": [
    "example"
   ],
   "properties": {
    "example": {
     "type": "object",
     "additionalProperties": true
    }
   }
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json"
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/cross-protocol-receipt-0642e574/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from phion.systems](https://www.zero.xyz/host/phion.systems/llms.txt)