# Optical Measurements - Schema Directionality

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

Compares closed export-field optical measurement records to detect directionality patterns in supplied schema data, providing analysis without independent certification.

## Facts

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

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 optical-measurements-schema-directionality-30bce626 -d '<json body>'
```

Example prompt: Compare my two sets of optical measurement records for schema directionality — the before set has my 5 baseline records and the after set has 3 updated records, both classified as public data with nonpersonal metadata only. Tell me if any export fields shifted direction.

## When to prefer this

Choose this endpoint when you need to programmatically compare two snapshots of optical measurement schema records to detect directionality changes in closed export fields, particularly when working with public or synthetic data that carries nonpersonal metadata. It is well-suited for pre-release validation, data pipeline audits, or compliance checks where schema field directionality must remain consistent across revisions. Use it over manual inspection when dealing with up to 32 records per snapshot and needing a structured, automated comparison output.

## Known failure modes

- Missing or empty 'before' array (minItems:1 required) returns validation error
- 'after' array exceeding 32 items or 'before' array exceeding 32 items returns schema error
- Invalid 'dataClass' value (must be 'public' or 'synthetic') causes rejection
- nonpersonalMetadata not set to true (const:true) causes request failure
- Payment of 0.035211 USDC not provided results in 402 Payment Required
- Malformed record objects in before/after arrays may result in analysis errors or empty results

## How this service works

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

## Output

Returns a structured analysis comparing the before and after arrays of optical measurement records, identifying directional shifts or inconsistencies in closed export fields. Output is a supplied-record analysis (not independent certification), flagging which fields changed direction, remained consistent, or are misaligned between the two snapshots.

## 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/optical-measurements-schema-directionality-30bce626/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)