# Spectrometry Records - Export Semantic Parity

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

Compares two sets of parsed spectrometry record projections for semantic equivalence, preserving pins and scope while ignoring record order.

## Facts

- Endpoint: POST https://www.mahastrategies.com/api/v1/compute/spectrometry-records/export-semantic-parity?utm_source=zero.xyz
- Price: $0.039317/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-25
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/spectrometry-records-export-semantic-parity-a1982beb
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_1zj-FHktSNFvBrf6RG-GC

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

Example prompt: Check whether my two sets of spectrometry records are semantically equivalent — ignoring any ordering differences — using public data class; here are the before array (up to 32 entries) and after array (up to 32 entries) I want compared.

## When to prefer this

Use this endpoint when you need to verify semantic equivalence between two versions of spectrometry record exports where ordering may differ but content should be preserved — particularly for instrument-pinned, calibration-pinned, or method-pinned spectrum records. Prefer this over raw byte comparison when record order is not meaningful and you care about logical content parity rather than exact byte equality. Not suitable for independent certification or proof-of-artifact verification.

## Known failure modes

- Array exceeds 32-item limit causing validation rejection
- Invalid dataClass value not matching 'public' or 'synthetic' enum
- nonpersonalMetadata not set to true (required const) causing schema rejection
- Malformed record objects in before/after arrays causing parse failure
- Empty or mismatched record types between before and after arrays

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

## Output

Returns a semantic parity assessment indicating whether the before and after spectrometry record arrays are equivalent when order is ignored, along with details on pin preservation, scope consistency, and any detected semantic differences between the typed record projections.

## 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/spectrometry-records-export-semantic-parity-a1982beb/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)