# Battery Measurements - Source Coverage Map

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

Binds battery measurement record references to an exact owner/subject/revision/content/source frame and maps source coverage across supplied records.

## Facts

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

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

Example prompt: Check the source coverage map for these 5 battery measurement rows against 3 source references using public data class — I need to confirm which rows are bound to an exact owner/revision/content-pin frame and flag any gaps.

## When to prefer this

Choose this endpoint when you need to audit or confirm source coverage bindings for battery measurement records — specifically linking rows to exact owner, revision, content-pin, and source frames. Best suited for battery cell-config, lot, or method-pinned record provenance workflows where you want to identify unbound or improperly sourced records. Prefer this over generic data validation endpoints when the domain is battery/energy measurement data and the concern is source-frame completeness rather than value correctness.

## Known failure modes

- rows array empty or exceeds 32-item limit — validation error returned
- sources array empty or exceeds 32-item limit — validation error returned
- dataClass not one of 'public' or 'synthetic' — schema rejection
- nonpersonalMetadata not set to true — request rejected
- malformed row or source reference — binding cannot be resolved, partial results or error
- source hash not matchable to supplied record — gap flagged rather than error

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

## Output

Returns a source coverage map showing which battery measurement rows are bound to exact owner/subject/revision/content/source frames, identifies unbound or partially covered records, and reports coverage gaps. Hash-shaped strings are treated as declarations, 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/battery-measurements-source-coverage-map-25e5a94b/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)