# Planetary Measurements Source Coverage Map

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

Binds planetary measurement records to a declared owner/subject/revision/content/source frame and maps source coverage across supplied rows and sources, returning hash-shaped declaration strings rather than independently verified data.

## Facts

- Endpoint: POST https://www.mahastrategies.com/api/v1/celestial/planetary-measurements/source-coverage-map?utm_source=zero.xyz
- Price: $0.035255/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-16
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/planetary-measurements-source-coverage-map-25d360ed
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_FSrWPtFfsoNx2AmYNuJVz

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 planetary-measurements-source-coverage-map-25d360ed -d '<json body>'
```

Example prompt: Can you run a source coverage map on these 12 planetary measurement rows against 3 declared sources, using public data class with nonpersonal metadata only, so I can see which rows have complete source bindings and which are missing coverage?

## When to prefer this

Choose this endpoint when you need to audit or map the declared source provenance of planetary or celestial measurement records — specifically to bind rows to owner/subject/revision/content/source frames and identify coverage gaps. It is not a data verification or certification service, only a declaration audit. Prefer this over generic hash-validation endpoints when your use case involves planetary measurement datasets with structured source tuples.

## Known failure modes

- Empty rows or sources array causes validation error
- rows or sources arrays exceeding 32 items rejected
- Missing required nonpersonal metadata flag (must be true) causes rejection
- Invalid dataClass value (must be 'public' or 'synthetic') causes schema error
- Malformed row or source references may produce incomplete bindings without explicit error
- Payment not processed results in x402 challenge response

## 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 target/site/convention/time/method-pinned planetary Supplied-record analysis, not independent certification. Full contract at the free describe URL.

## Output

Returns a source coverage map binding each supplied row to its declared owner, subject, revision, content, and source frame. Hash-shaped strings represent declarations (not independently certified source bytes). Flags rows with missing or incomplete source coverage. Does not independently verify source content — output is a declaration audit, not certification.

## 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/planetary-measurements-source-coverage-map-25d360ed/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)