# Scientific Dataset Records - Source Coverage Map

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

Binds scientific dataset record references to an exact owner/subject/revision/content/source frame and maps source coverage across supplied rows and sources.

## Facts

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

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 scientific-dataset-records-source-coverage-map-e5efcbb6 -d '<json body>'
```

Example prompt: Can you map the source coverage for these 10 scientific dataset rows against my 5 declared sources — classify the data as public and confirm this is nonpersonal metadata only?

## When to prefer this

Use this endpoint when you need to map declared source coverage across a bounded set of scientific dataset records (up to 32 rows and 32 sources) against exact owner/subject/revision/content pins. It is appropriate for nonpersonal, public or synthetic data analysis where you need a structured coverage declaration rather than independent certification. Prefer this over generic validation tools when working specifically with scientific dataset manifests that require source-frame binding.

## Known failure modes

- Rows or sources array exceeds maxItems limit of 32 — request rejected
- Missing required nonpersonalMetadata:true field — validation error
- Invalid dataClass value outside enum [public, synthetic] — schema validation failure
- Empty rows or sources arrays (below minItems:1) — request rejected
- Ambiguous or hash-shaped strings that cannot be resolved to declared source frames — partial coverage map returned
- Timeout if payload is near the maximum array sizes

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

## Output

Returns a source coverage map that binds each supplied dataset record row to its declared owner, subject, revision, content, and source frame. The response indicates which rows are covered by which sources and flags any missing or unmatched bindings. Results are declared-record analysis, not independently certified 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/scientific-dataset-records-source-coverage-map-e5efcbb6/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)