# Orbital Records - Export Semantic Parity

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

Compares two sets of parsed typed orbital record projections for semantic equality, preserving pins and scope (target, centre, frame, time-scale, solution) while ignoring field order.

## Facts

- Endpoint: POST https://www.mahastrategies.com/api/v1/celestial/orbital-records/export-semantic-parity?utm_source=zero.xyz
- Price: $0.039328/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-export-semantic-parity-5412f2a3
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_uXR6I0_3RoQIwcMhM49nn

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-export-semantic-parity-5412f2a3 -d '<json body>'
```

Example prompt: Can you check whether these two sets of orbital record projections are semantically equivalent — compare the before array (up to 32 entries) against the after array (up to 32 entries) using public data class, and confirm all target, centre, frame, time-scale, and solution pins are preserved even if the field order changed?

## When to prefer this

Choose this endpoint when you need to confirm that two versions of parsed typed orbital record projections are semantically identical — specifically preserving target, centre, frame, time-scale, and solution pins — while tolerating field-order differences. It is not a raw-byte equality check and does not certify the underlying orbital artifact; use it for scope-level comparison of supplied records after a transformation, migration, or revision handoff.

## Known failure modes

- Arrays exceed 32-item limit — request rejected
- dataClass value outside 'public' or 'synthetic' enum — validation error
- nonpersonalMetadata not set to true — contract violation
- Malformed or unparseable record entries in before/after arrays — parsing error
- Empty or mismatched array structures causing inconclusive comparison

## How this service works

Compare parsed typed record projections, preserving all pins and scope while ignoring order; not raw-byte equality or proof of the underlying artifact for target/centre/frame/time-scale/solution-pinned orbital Supplied-record analysis, not independent certification. Full contract at the free describe URL.

## Output

Returns a semantic parity assessment between the before and after orbital record projection arrays, indicating whether the two sets are equivalent when ignoring field order, with details on any mismatches in pinned fields (target, centre, frame, time-scale, solution). Does not certify the underlying artifact — scope is limited to supplied-record analysis.

## Request schema (JSON Schema)

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

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/orbital-records-export-semantic-parity-5412f2a3/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)