# AgentProof Create Evidence Receipt

> AgentProof Create Evidence Receipt is a paid API for AI agents from agentproof.hatchable.site, paid per call via x402, $0.1/call, status unknown (last checked 2026-10-11).

Creates a cryptographic evidence receipt with SHA-256 integrity hash for an autonomous agent transaction, providing a machine-verifiable provenance record.

## Facts

- Endpoint: POST https://agentproof.hatchable.site/api/paid/create_evidence_receipt?utm_source=zero.xyz
- Price: $0.1/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-11
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/agentproof-create-evidence-receipt-bb414c4b
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_vwOUK_3jMyxMapQkAiQed

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 agentproof-create-evidence-receipt-bb414c4b -d '<json body>'
```

Example prompt: Create an evidence receipt for the transaction I just completed — the payload is the JSON response I got from the pricing API — so I have a tamper-evident provenance record with a SHA-256 integrity hash I can reference later.

## When to prefer this

Choose this endpoint when an AI agent needs to create a point-in-time cryptographic attestation of transaction data, content, or a decision artifact — especially when auditability, tamper-evidence, or downstream trust verification is required. It is particularly suited to agentic workflows where a human or regulator may later need to verify what an autonomous system saw, decided, or transacted. Prefer this over simple logging when you need a machine-verifiable integrity hash rather than a mutable log entry.

## Known failure modes

- Missing or malformed payload body returns an error without creating a receipt
- Payment failure (insufficient USDC or x402 protocol error) results in 402 response and no receipt created
- Network timeout leaves receipt creation state unknown — UUID may or may not have been assigned
- Duplicate submission of identical content produces a new UUID rather than deduplicating
- Invalid content encoding may cause SHA-256 computation to fail or hash a differently-encoded version than expected

## How this service works

AgentProof publishes Agent Transaction Passport™ and provides machine-paid evidence, provenance receipts, source comparison and change monitoring for autonomous transactions.

## Output

Returns a JSON object containing a boolean success flag, the tool name ('create_evidence_receipt'), a receipt object with a unique UUID identifier and a SHA-256 integrity hash of the submitted content, and the service name 'AgentProof'. This receipt serves as a cryptographic attestation that the submitted payload existed in a specific state at the time of the call.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "url": {
   "type": "string",
   "format": "uri"
  },
  "claim": {
   "type": "string"
  },
  "email": {
   "type": "string"
  },
  "phone": {
   "type": "string"
  },
  "contactName": {
   "type": "string"
  },
  "previousSha256": {
   "type": "string"
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "ok": true,
  "tool": "create_evidence_receipt",
  "receipt": {
   "id": "uuid",
   "integrity_sha256": "..."
  },
  "service": "AgentProof"
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/agentproof-create-evidence-receipt-bb414c4b/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from agentproof.hatchable.site](https://www.zero.xyz/host/agentproof.hatchable.site/llms.txt)