# R/IV Provenance Receipt

> R/IV Provenance Receipt is a paid API for AI agents from rdiv-commerce-router-production.up.railway.app, paid per call via x402, $0.1/call, status unknown (last checked 2026-10-29).

Issues a signed evidence-provenance receipt for a job or artifact, linking it to source records without asserting truth.

## Facts

- Endpoint: POST https://rdiv-commerce-router-production.up.railway.app/x402/execute/provenance.receipt?utm_source=zero.xyz
- Price: $0.1/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-29
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/r-iv-provenance-receipt-7d939991
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_DVPSaFezkk6cs_lbvN-dE

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 r-iv-provenance-receipt-7d939991 -d '<json body>'
```

Example prompt: Generate a signed provenance receipt for the report I just produced — the artifact is the draft labeled 'market-analysis-v2' and the source records are the three datasets we pulled from earlier, so auditors can trace exactly where each claim came from.

## When to prefer this

Use this endpoint when you need a cryptographically signed, timestamped record of what source data was used to produce an AI job or artifact — especially for audit, compliance, or chain-of-custody requirements. Prefer this over generic logging when you need an externally verifiable, signed attestation rather than an internal record. This is not a fact-checking or truth-verification service; choose it when the goal is provenance traceability, not content accuracy validation.

## Known failure modes

- Missing required fields (job_or_artifact or source_records omitted) returns a 400-level error
- Empty or malformed source_records array may result in an incomplete or rejected receipt
- Payment failure via x402 protocol blocks execution before receipt generation
- Upstream signing service unavailability causes timeout or 5xx response
- Duplicate request_id may cause idempotency conflicts depending on server behavior

## How this service works

R/IV provenance.receipt — Provide a signed evidence-provenance receipt; not proof of truth.

## Output

A signed provenance receipt object that cryptographically links the submitted job or artifact to its declared source records, serving as an evidence trail. The receipt attests to what inputs were associated with what output at a given time, but explicitly does not assert the truth or accuracy of the content itself.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "input": {
   "type": "object",
   "required": [
    "job_or_artifact",
    "source_records"
   ],
   "properties": {
    "request_id": {
     "type": "string"
    },
    "source_records": {
     "type": "array"
    },
    "job_or_artifact": {
     "type": "object"
    }
   },
   "additionalProperties": true
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/r-iv-provenance-receipt-7d939991/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from rdiv-commerce-router-production.up.railway.app](https://www.zero.xyz/host/rdiv-commerce-router-production.up.railway.app/llms.txt)