# Battery Measurements Provenance Edge Audit

> Battery Measurements Provenance Edge Audit is a paid API for AI agents from www.mahastrategies.com, paid per call via x402, $0.045322/call, status unknown (last checked 2026-10-20).

Binds battery measurement rows to exact dataset, material, lot, method, source-revision, and content manifests to verify provenance consistency without certifying experimental results.

## Facts

- Endpoint: POST https://www.mahastrategies.com/api/v1/compute/battery-measurements/provenance-edge-audit?utm_source=zero.xyz
- Price: $0.045322/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-provenance-edge-audit-2937b397
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_BO0pNl8nJ2UzK5S0Qd1Gx

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-provenance-edge-audit-2937b397 -d '<json body>'
```

Example prompt: Audit the provenance of these battery measurement rows — I have up to 20 rows of public-class measurement data and 5 source references, and I need to confirm they bind correctly to the declared dataset, material lot, method, and content manifests.

## When to prefer this

Choose this endpoint when you need to audit whether battery measurement rows are correctly bound to their provenance manifests (dataset, material, lot, method, source-revision, content) for traceability purposes. Use it for data supply chain verification in battery research workflows, not for statistical analysis or experimental certification. Prefer this over generic data validation tools when the specific domain is battery measurements and the concern is provenance-chain integrity rather than data quality.

## Known failure modes

- Input rows array is empty or exceeds 32-item limit — validation error returned
- Sources array missing or exceeds 32 items — request rejected
- dataClass not set to 'public' or 'synthetic' — enum validation failure
- nonpersonalMetadata not set to boolean true — const validation failure
- Manifest pins present but unresolvable against provided sources — partial match report
- Malformed row structure causing binding failure — row-level error in response

## How this service works

Bind measurement rows to exact dataset/material/lot/method/source-revision/content manifests; matching pins do not prove experimental Supplied-record analysis, not independent certification. Full contract at the free describe URL.

## Output

Returns a provenance binding report indicating which measurement rows successfully match their declared dataset, material, lot, method, source-revision, and content manifests, flagging any mismatches or unresolvable pins. Does not independently certify experimental results.

## 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-provenance-edge-audit-2937b397/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)