# Settlement Receipts - Provenance Edge Audit

> Settlement Receipts - Provenance Edge Audit is a paid API for AI agents from www.mahastrategies.com, paid per call via x402, $0.045301/call, status unknown (last checked 2026-10-20).

Binds retained-result metadata edges to supplied receipt result pins within a payment/network settlement frame, auditing provenance linkages without delivery certification.

## Facts

- Endpoint: POST https://www.mahastrategies.com/api/v1/verify/settlement-receipts/provenance-edge-audit?utm_source=zero.xyz
- Price: $0.045301/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-20
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/settlement-receipts-provenance-edge-audit-101828d9
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_TqPyxktMdqep8VZjy5o9K

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 settlement-receipts-provenance-edge-audit-101828d9 -d '<json body>'
```

Example prompt: Audit the provenance edge bindings for these 3 settlement receipts and their result pins — data class is 'synthetic' and all metadata is nonpersonal — and tell me which pins are bound and which remain unbound.

## When to prefer this

Choose this endpoint when you need to audit and bind provenance metadata edges to settlement receipt result pins in a payment or network settlement context, particularly when working with nonpersonal, offline typed metadata. Prefer this over generic receipt verification when you specifically need edge-level provenance linkage analysis within a structured settlement frame. Not suitable for delivery certification, personal data, or real-time payment execution.

## Known failure modes

- Null result pins remain unbound regardless of receipt confirmation status — no error raised, just unbound status returned
- Input arrays exceeding 32 items or fewer than 1 item are rejected
- dataClass must be one of 'public' or 'synthetic'; invalid enum values cause rejection
- nonpersonalMetadata must be explicitly set to true; omission or false value causes rejection
- Mismatched array lengths between edges, results, and receipts may result in partial binding outcomes
- Service may return no delivery certification even on successful binding

## How this service works

Bind retained-result metadata edges to supplied receipt result pins in an exact payment/network frame. Null result pins stay unbound even for a declared confirmed receipt; no delivery certification. Offline typed nonpersonal metadata only. Result retention: 24 hours; minimal receipt metadata: 90 days.

## Output

Returns the outcome of binding metadata edges to receipt result pins within the settlement frame, indicating which pins are successfully bound and which remain unbound (null pins stay unbound even for confirmed receipts). Result data is retained for 24 hours; minimal receipt metadata is retained for 90 days. No delivery certification is provided.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "edges": {
   "type": "array",
   "maxItems": 32,
   "minItems": 1
  },
  "results": {
   "type": "array",
   "maxItems": 32,
   "minItems": 1
  },
  "receipts": {
   "type": "array",
   "maxItems": 32,
   "minItems": 1
  },
  "dataClass": {
   "enum": [
    "public",
    "synthetic"
   ],
   "type": "string"
  },
  "nonpersonalMetadata": {
   "type": "boolean",
   "const": true
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/settlement-receipts-provenance-edge-audit-101828d9/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from www.mahastrategies.com](https://www.zero.xyz/host/www.mahastrategies.com/llms.txt)