# Settlement Receipts — Source Coverage Map

> Settlement Receipts — Source Coverage Map is a paid API for AI agents from www.mahastrategies.com, paid per call via x402, $0.035075/call, status unknown (last checked 2026-10-15).

Binds receipt payment and quote pins to supplied purchase metadata on the same network, mapping which receipts have corresponding source coverage without validating on-chain authorization events.

## Facts

- Endpoint: POST https://www.mahastrategies.com/api/v1/verify/settlement-receipts/source-coverage-map?utm_source=zero.xyz
- Price: $0.035075/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-15
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/settlement-receipts-source-coverage-map-82251dae
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_Hm66CXFiMCYKmYoocE1Sf

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-source-coverage-map-82251dae -d '<json body>'
```

Example prompt: Can you map these 12 settlement receipts against our purchase metadata to see which ones have source coverage on the same network? Use public data class and flag any receipt pins that don't have a matching purchase entry.

## When to prefer this

Use this endpoint when you need to systematically map which settlement receipts have corresponding source coverage in your purchase metadata, specifically when operating on the same network. Prefer this over generic receipt validation when you need pin-level binding analysis rather than on-chain authorization checks. Best suited for offline, non-personal metadata reconciliation workflows where amount alone is insufficient for identity matching.

## Known failure modes

- Missing required nonpersonalMetadata: true field causes rejection
- Array size exceeds 32 items for receipts or purchases, triggering validation error
- Mismatch between receipt network and purchase metadata network yields empty or partial coverage map
- Invalid dataClass value (not 'public' or 'synthetic') causes schema validation failure
- Empty receipts or purchases arrays (below minItems: 1) cause request rejection
- Result expiry after 24 hours means detailed data is no longer retrievable

## How this service works

Bind receipt payment and quote pins to supplied purchase metadata on the same network. Amount alone is not identity; this does not validate an on-chain authorization event or product attribution. Offline typed nonpersonal metadata only. Result retention: 24 hours; minimal receipt metadata: 90 days.

## Output

Returns a source coverage map indicating which supplied receipts have corresponding purchase metadata pins on the same network, including which receipt/quote pins are bound or missing. Full results retained for 24 hours; minimal receipt metadata retained for 90 days. Does not validate on-chain authorization events or product attribution.

## Request schema (JSON Schema)

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

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/settlement-receipts-source-coverage-map-82251dae/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)