# Edition Records Source Coverage Map

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

Maps supplied edition record rows to their declared owner/subject/revision/content/source frame, producing a structured coverage analysis of which sources are bound to which edition pins.

## Facts

- Endpoint: POST https://www.mahastrategies.com/api/v1/library/edition-records/source-coverage-map?utm_source=zero.xyz
- Price: $0.035315/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-20
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/edition-records-source-coverage-map-9daff5fd
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_GUrE08XlRUJiEKhCDg9hF

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 edition-records-source-coverage-map-9daff5fd -d '<json body>'
```

Example prompt: Can you map these 10 edition record rows to their declared source coverage frame — the data class is public and all metadata is non-personal — and show me which sources are bound to which owner/revision/content pins?

## When to prefer this

Use this endpoint when you need to analyze the declared source coverage frame for a batch of edition records — specifically when you need to understand which sources are bound to owner/subject/revision/content pins for publisher/work/edition combinations. Prefer this over generic metadata lookup when you need a structured coverage map from supplied record data rather than a live database query.

## Known failure modes

- Missing required nonpersonalMetadata:true flag causes rejection
- rows or sources arrays outside 1–32 item bounds return validation errors
- Invalid dataClass value (not 'public' or 'synthetic') causes schema rejection
- Malformed record rows that cannot be parsed into edition frame components may return incomplete coverage mappings
- Payment failure via x402 protocol results in 402 response with no data returned

## How this service works

Bind record references to an exact owner/subject/revision/content/source frame; hash-shaped strings are declarations, not independently verified source bytes for publisher/work/edition/format/revision-pinned edition Supplied-record analysis, not independent certification. Full contract at the free describe URL.

## Output

Returns a structured source coverage map that binds each supplied edition record row to its declared owner/subject/revision/content/source frame, showing which sources are associated with each edition pin. The analysis reflects declared bindings from the supplied records, not independently verified source bytes.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "rows": {
   "type": "array",
   "maxItems": 32,
   "minItems": 1
  },
  "sources": {
   "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/edition-records-source-coverage-map-9daff5fd/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)