# Optical Measurements - Export Semantic Parity

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

Compares two sets of parsed optical measurement record projections (before/after) for semantic parity, preserving pins and scope while ignoring record order.

## Facts

- Endpoint: POST https://www.mahastrategies.com/api/v1/compute/optical-measurements/export-semantic-parity?utm_source=zero.xyz
- Price: $0.039323/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-export-semantic-parity-f712343d
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_EPIfT6Ffy-qH-U5QuaYpq

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

Example prompt: Can you check semantic parity between these two optical measurement record sets — the before array has our original calibration projections and the after array has the exported versions — using public data class, and confirm they match ignoring any reordering of records?

## When to prefer this

Choose this endpoint when you need to verify that two sets of optical measurement record projections are semantically equivalent after a transformation, export, or pipeline step — particularly when record ordering may have changed but pin and scope integrity must be confirmed. Prefer this over raw-byte diff tools when you care about semantic equivalence rather than exact byte-for-byte matching, and over general-purpose diff utilities when your records are optical geometry, calibration, lot, or method-pinned measurement data.

## Known failure modes

- Array exceeds 32-item limit — request rejected with validation error
- dataClass value not in allowed enum (public/synthetic) — schema validation failure
- nonpersonalMetadata not set to true (const constraint) — request rejected
- Malformed record projections in before/after arrays — parsing error or partial result
- Empty arrays on both sides — trivially equal result with no useful diff
- Network timeout for large or complex record sets

## 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 optical geometry/calibration/lot/method-pinned Supplied-record analysis, not independent certification. Full contract at the free describe URL.

## Output

Returns a semantic parity assessment between the before and after optical measurement record arrays, indicating whether the pin-preserved, scope-matched projections are equivalent when order is disregarded. Highlights any meaningful discrepancies in calibration, lot, or method-pinned fields without performing raw-byte comparison or independent artifact certification.

## 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/optical-measurements-export-semantic-parity-f712343d/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)