# Planetary Measurements - Schema Directionality

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

Compares closed export-field directionality in supplied planetary measurement schema records, flagging mismatches between before and after field states.

## Facts

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

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 planetary-measurements-schema-directionality-fdba540b -d '<json body>'
```

Example prompt: Compare the directionality of closed export fields in my planetary measurement schema — I have a before snapshot with fields ['mass','orbit','period'] and an after snapshot with ['mass','period','orbit'], using public data class, and I want to know if any field directions have flipped.

## When to prefer this

Use this endpoint when you need to audit the directional consistency of closed export fields in planetary measurement schema declarations between two snapshots (before/after states). Prefer this over generic schema diff tools when working specifically with celestial/planetary structured records that require export-field directionality analysis rather than raw content comparison.

## Known failure modes

- before array is empty or missing required minimum items — returns validation error
- after array exceeds 32 item limit — returns schema constraint error
- dataClass not one of 'public' or 'synthetic' — returns enum validation error
- nonpersonalMetadata not set to true (const constraint) — returns rejection
- malformed array items in before or after fields — returns parse 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 structured report identifying directionality mismatches between the before and after export-field arrays in the supplied planetary measurement schema record, including which fields changed direction and a summary of comparison findings. Does not perform independent certification.

## 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/planetary-measurements-schema-directionality-fdba540b/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)