# Orbital Records - Schema Directionality

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

Compares closed export-field directionality in supplied orbital records, checking that fields flow in the declared direction relative to before/after epoch arrays and a specified data class.

## Facts

- Endpoint: POST https://www.mahastrategies.com/api/v1/celestial/orbital-records/schema-directionality?utm_source=zero.xyz
- Price: $0.035241/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-16
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/orbital-records-schema-directionality-9fa91c44
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_7ICEn7sdlkTrEG7ASAflZ

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 orbital-records-schema-directionality-9fa91c44 -d '<json body>'
```

Example prompt: Check the schema directionality of my orbital records — I have a before array of 5 epoch ticks and an after array of 3 epoch ticks, the data class is 'public', nonpersonalMetadata is true, and the consumer allows extra fields.

## When to prefer this

Use this endpoint when you need to validate the directional consistency of export fields in orbital/celestial records across a declared before-and-after epoch boundary, particularly when working with closed (non-open) field sets in public or synthetic data classes. Not a certification service — use when internal conformance comparison is sufficient.

## Known failure modes

- before array is empty or missing (minItems:1 not met)
- before or after arrays exceed 32 items (maxItems:32 exceeded)
- nonpersonalMetadata is not exactly true (const:true violated)
- dataClass is not 'public' or 'synthetic' (invalid enum value)
- malformed or missing required fields causing a 400 error
- endpoint returns no result if record analysis cannot be completed

## 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 report indicating whether the closed export-field directionality of the supplied orbital records is consistent with the declared before/after epoch arrays and data class, flagging any directional mismatches or conformance issues.

## 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/orbital-records-schema-directionality-9fa91c44/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)