# Payment Quotes - Source Coverage Map

> Payment Quotes - Source Coverage Map is a paid API for AI agents from www.mahastrategies.com, paid per call via x402, $0.035069/call, status unknown (last checked 2026-10-19).

Binds payment quote resources to exact offer revision manifests, producing a declared source coverage map for offline metadata validation only.

## Facts

- Endpoint: POST https://www.mahastrategies.com/api/v1/verify/payment-quotes/source-coverage-map?utm_source=zero.xyz
- Price: $0.035069/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-19
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/payment-quotes-source-coverage-map-716bd877
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_qjgw5rWBlbB9ciNwT7MSO

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 payment-quotes-source-coverage-map-716bd877 -d '<json body>'
```

Example prompt: Can you bind these payment quotes to their offer revision manifests and give me the source coverage map? I have up to 10 quotes and 10 offers, all using public data class, and I just need declared coverage — not a live availability or payability check.

## When to prefer this

Use this endpoint when you need to declaratively validate whether a set of payment quotes are bound to specific offer revision manifests for auditing, reconciliation, or coverage reporting purposes. It is the right choice when you only need offline metadata validation — not live quote availability, payability, or delivery status. Prefer this over live quote-check endpoints when your data is public or synthetic and nonpersonal, and when you need a persistent receipt for 90 days.

## Known failure modes

- Mismatched quote or offer array sizes or formats return a validation error
- Providing more than 32 items in either the quotes or offers array returns a limit exceeded error
- Omitting the nonpersonalMetadata: true constant causes a schema rejection
- Using an invalid dataClass value (anything other than 'public' or 'synthetic') returns an enum error
- Supplying personally identifiable information causes rejection as only nonpersonal metadata is accepted
- Result not found after 24 hours — results expire and must be regenerated

## How this service works

Bind supplied quote resource pins to exact offer revision manifests. This is declared source coverage, not a live quote, availability, payability or delivery check. Offline typed nonpersonal metadata only. Result retention: 24 hours; minimal receipt metadata: 90 days.

## Output

Returns a source coverage manifest showing which supplied quote resources are bound to which offer revision manifests, including binding status, digest or pin matches, and receipt metadata. Results are retained for 24 hours; minimal receipt metadata is retained for 90 days. This is a declared coverage result only — not a live availability, payability, or delivery check.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "offers": {
   "type": "array",
   "maxItems": 32,
   "minItems": 1
  },
  "quotes": {
   "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/payment-quotes-source-coverage-map-716bd877/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)