# Thermal Measurements - Schema Directionality Analysis

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

Compares closed export-field supplied-record thermal measurements for schema directionality, validating before/after record arrays against a declared data class

## Facts

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

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-schema-directionality-analysis-6e589c17 -d '<json body>'
```

Example prompt: Compare these two sets of thermal measurement records for schema directionality — my before-set has 5 records and my after-set has 3 records, using the 'synthetic' data class with nonpersonal metadata only.

## When to prefer this

Use this endpoint when you need to validate the directional consistency of closed export fields across paired thermal measurement record sets, particularly when working with before/after snapshots of sensor data and need schema-level directionality assurance rather than full certification. Prefer this over generic diff tools when the data class (public or synthetic) and nonpersonal metadata constraints are key to the comparison.

## Known failure modes

- before array empty or exceeds 32 items — validation error
- after array missing or exceeds 32 items — validation error
- nonpersonal metadata not set to true — rejected as required const
- invalid dataClass value outside 'public' or 'synthetic' enum — schema rejection
- malformed record entries in before/after arrays — parse error
- payment not included or insufficient — 402 response

## How this service works

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

## Output

Returns a schema directionality comparison result for the supplied before/after thermal record arrays, indicating whether closed export fields align directionally, any mismatches or anomalies in field structure, and conformance status relative to the declared data class and metadata constraints.

## 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/thermal-measurements-schema-directionality-analysis-6e589c17/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)