# Reaction Records - Source Coverage Map

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

Binds reaction record references to an exact owner/subject/revision/content/source frame to verify declared source coverage metadata against supplied rows and sources.

## Facts

- Endpoint: POST https://www.mahastrategies.com/api/v1/compute/reaction-records/source-coverage-map?utm_source=zero.xyz
- Price: $0.035165/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-16
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/reaction-records-source-coverage-map-ae945233
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_ePaDvIXqHSeG6EwgMb_bF

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 reaction-records-source-coverage-map-ae945233 -d '<json body>'
```

Example prompt: Can you check the source coverage map for these 10 reaction record rows against our supplied sources — they're classified as synthetic data with nonpersonal metadata only — and tell me whether their owner, subject, revision, and content declarations are correctly bound?

## When to prefer this

Use this endpoint when you need to validate that reaction record rows are correctly bound to specific source coverage frames — particularly owner, subject, revision, and content metadata — for public or synthetic datasets where nonpersonal metadata can be asserted. Prefer this over generic validation tools when the domain is specifically reaction records and you need a structured source-coverage-map output rather than independent byte-level certification.

## Known failure modes

- Invalid or missing rows array (minItems:1 violated)
- More than 32 rows or sources supplied (maxItems:32 exceeded)
- dataClass not one of 'public' or 'synthetic'
- nonpersonalMetadata not set to true (const constraint)
- Malformed record references causing binding failures
- Network timeout or 402 payment failure

## 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 dataset/reaction/method/revision Supplied-record analysis, not independent certification. Full contract at the free describe URL.

## Output

Returns a source coverage map indicating whether each supplied row is correctly bound to the declared owner, subject, revision, content, and source frame. Results flag which bindings match, which are missing, and which declarations are inconsistent — presented as declared-record analysis, not independent certification of the underlying 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/reaction-records-source-coverage-map-ae945233/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)