# Battery Measurements - Required Field Coverage Check

> Battery Measurements - Required Field Coverage Check is a paid API for AI agents from www.mahastrategies.com, paid per call via x402, $0.010141/call, status unknown (last checked 2026-10-20).

Checks whether required scientific fields (dataset, method, revision, content pins) are present in supplied battery measurement records, treating null as missing rather than invalid.

## Facts

- Endpoint: POST https://www.mahastrategies.com/api/v1/compute/battery-measurements/required-field-coverage?utm_source=zero.xyz
- Price: $0.010141/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-20
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/battery-measurements-required-field-coverage-check-9b420abc
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_y3zA4t1-uklmIzuYICmXM

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-required-field-coverage-check-9b420abc -d '<json body>'
```

Example prompt: Can you check these 20 battery measurement rows to make sure all the required fields — dataset, method, revision, and content pins — are actually present? The data is synthetic and has no personal metadata. Flag any rows where those pins are null.

## When to prefer this

Choose this endpoint when you need a fast, cheap pre-flight check to confirm required scientific pins are non-null in battery measurement records before running deeper analysis or certification workflows. It is specifically scoped to battery/cell-config/lot/method-pinned data and treats null strictly as missing — not as an invalid credential.

## Known failure modes

- Rows array empty or exceeds 32-item limit — validation error
- dataClass not one of 'public' or 'synthetic' — enum validation failure
- nonpersonalMetadata not explicitly set to true — request rejected
- requiredFields array empty or exceeds 8 fields — schema violation
- Malformed row objects missing expected structure — partial or error response

## How this service works

Check presence of required scientific dataset/method/revision/content pins; null is missing, not an invalid credential or artifact for battery/cell-config/lot/method-pinned Supplied-record analysis, not independent certification. Full contract at the free describe URL.

## Output

Returns a field-coverage report per supplied row indicating which required pins (dataset, method, revision, content) are present or null/missing, without independently certifying the underlying data artifacts.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "rows": {
   "type": "array",
   "maxItems": 32,
   "minItems": 1
  },
  "dataClass": {
   "enum": [
    "public",
    "synthetic"
   ],
   "type": "string"
  },
  "requiredFields": {
   "type": "array",
   "maxItems": 8,
   "minItems": 1
  },
  "nonpersonalMetadata": {
   "type": "boolean",
   "const": true
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/battery-measurements-required-field-coverage-check-9b420abc/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)