# Thermal Measurements Source Coverage Map

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

Binds thermal measurement records to a declared owner/subject/revision/content/source frame and maps source coverage across supplied rows and sources for a given data class.

## Facts

- Endpoint: POST https://www.mahastrategies.com/api/v1/compute/thermal-measurements/source-coverage-map?utm_source=zero.xyz
- Price: $0.035213/call
- Payment: x402
- Status: unknown
- Last checked: 2026-11-04
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/thermal-measurements-source-coverage-map-3edc3a80
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_ley-srQZd-TvHJSEXbRu3

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 thermal-measurements-source-coverage-map-3edc3a80 -d '<json body>'
```

Example prompt: Map source coverage for these 15 thermal measurement rows against 4 declared sources, treating the data as synthetic and non-personal — I need to know which source frame each record binds to before I run the audit export.

## When to prefer this

Choose this endpoint when you need to systematically map a batch of thermal measurement records to their declared source frame before an audit, export, or reconciliation step. It is purpose-built for thermal lot/method/revision-pinned source attribution and is most useful when you have both measurement rows and source references ready and need a structured coverage report. Prefer alternatives if you need independent certification of source data integrity rather than declared-binding analysis.

## Known failure modes

- rows or sources array exceeds 32-item limit — request rejected
- nonpersonalMetadata must be exactly true — any other value fails validation
- dataClass must be one of 'public' or 'synthetic' — unrecognized values return error
- empty rows or sources arrays rejected (minItems: 1)
- malformed row or source entries may result in partial coverage map or binding errors
- payment failure via x402 protocol causes request not to be processed

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

## Output

Returns a structured source coverage map linking each supplied measurement row to its declared owner, subject, revision, content, and source frame. Indicates which rows are bound, which sources cover which records, and flags any coverage gaps. Does not independently verify source bytes — it reflects declared bindings only.

## 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/thermal-measurements-source-coverage-map-3edc3a80/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)