# Telescope Calibrations - Export Semantic Parity

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

Compares two sets of parsed telescope calibration record projections for semantic parity, checking that instrument/detector/filter/binning/readout/pipeline pins and scope match while ignoring record order.

## Facts

- Endpoint: POST https://www.mahastrategies.com/api/v1/celestial/telescope-calibrations/export-semantic-parity?utm_source=zero.xyz
- Price: $0.03933/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-16
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/telescope-calibrations-export-semantic-parity-622a7143
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_kw5cpIyoFGP5ViFj5wOmv

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 telescope-calibrations-export-semantic-parity-622a7143 -d '<json body>'
```

Example prompt: Check whether these two sets of telescope calibration records are semantically equivalent — compare the before and after arrays for a synthetic data class, ignoring record order but preserving all instrument, detector, filter, binning, readout, and pipeline pins.

## When to prefer this

Choose this endpoint when you need order-agnostic semantic equivalence checking of telescope calibration record projections pinned to specific instrument/detector/filter/binning/readout/pipeline parameters, and you do not need raw-byte equality or cryptographic proof of the underlying artifact. Prefer this over byte-level diff tools when calibration records may be reordered but semantically unchanged.

## Known failure modes

- Arrays exceed 32 items — request rejected with validation error
- dataClass not one of 'public' or 'synthetic' — enum validation failure
- nonpersonalMetadata not exactly true — const validation failure
- Empty or malformed arrays — may return trivial parity result or error
- Network timeout for large comparison payloads

## 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 instrument/detector/filter/binning/readout/pipeline-pinned calibration Supplied-record analysis, not independent certification. Full contract at the free describe URL.

## Output

Returns a semantic parity analysis indicating whether the before and after calibration record sets are equivalent with respect to all declared pins (instrument, detector, filter, binning, readout, pipeline) and scope, while ignoring record order. Reports any mismatches in pins or scope between the two sets.

## 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/telescope-calibrations-export-semantic-parity-622a7143/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)