# Battery Measurements - Schema Directionality

> Battery Measurements - Schema Directionality is a paid API for AI agents from www.mahastrategies.com, paid per call via x402, $0.035205/call, status unknown (last checked 2026-10-16).

Compares schema directionality of closed export-field battery measurement records, validating field-level directional consistency between before/after record sets.

## Facts

- Endpoint: POST https://www.mahastrategies.com/api/v1/compute/battery-measurements/schema-directionality?utm_source=zero.xyz
- Price: $0.035205/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-16
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/battery-measurements-schema-directionality-be966fd4
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_VxRGLdjUXfSzRCmGmNKKU

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-schema-directionality-be966fd4 -d '<json body>'
```

Example prompt: Compare the directionality of these battery measurement records — I have up to 32 'before' entries and up to 32 'after' entries using public data class, with nonpersonal metadata only, and I want to know if any export fields changed direction.

## When to prefer this

Choose this endpoint when you need to validate or compare the directional consistency of schema fields in battery measurement export records across a before/after snapshot pair, especially when working with closed export fields and need to ensure field directionality has not shifted between record states. Prefer this over general schema diff tools when the domain is specifically battery measurement data with nonpersonal metadata constraints.

## Known failure modes

- Empty or missing 'before' array (minItems:1 violated) returns validation error
- Array length exceeding 32 items for either before or after returns schema rejection
- Invalid dataClass value outside ['public','synthetic'] enum causes request failure
- nonpersonal Metadata not set to true (const:true) causes rejection
- Malformed or non-boolean consumerAllowsExtraFields triggers schema error

## How this service works

Compare closed export-field Supplied-record analysis, not independent certification. Full contract at the free describe URL.

## Output

Returns a comparison analysis of schema field directionality between the supplied before and after battery measurement record arrays, identifying any fields that have changed directional orientation, along with coverage and consistency details for the export field set.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "after": {
   "type": "array",
   "maxItems": 32,
   "minItems": 0
  },
  "before": {
   "type": "array",
   "maxItems": 32,
   "minItems": 1
  },
  "dataClass": {
   "enum": [
    "public",
    "synthetic"
   ],
   "type": "string"
  },
  "nonpersonalMetadata": {
   "type": "boolean",
   "const": true
  },
  "consumerAllowsExtraFields": {
   "type": "boolean"
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/battery-measurements-schema-directionality-be966fd4/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)