# Ceramic Measurements - Export Semantic Parity

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

Compares two sets of parsed ceramic measurement record projections for semantic parity, preserving pins and scope while ignoring field order.

## Facts

- Endpoint: POST https://www.mahastrategies.com/api/v1/compute/ceramic-measurements/export-semantic-parity?utm_source=zero.xyz
- Price: $0.039321/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-20
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/ceramic-measurements-export-semantic-parity-00024411
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_DI5n232SNEFXO_1SMnSyc

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

Example prompt: Can you check if these two sets of ceramic measurement records are semantically equivalent — I have up to 20 records in the 'before' list and 18 in the 'after' list, both classified as 'public' data with nonpersonal metadata only, and I need to know if all pins and scope are preserved even if the field order changed?

## When to prefer this

Choose this endpoint when you need to confirm that two versions of ceramic measurement record exports are semantically equivalent — specifically when field ordering may have changed but pin and scope integrity must be preserved. Prefer this over raw byte-comparison tools when order-agnostic semantic equivalence is the goal. Use only with public or synthetic dataClass ceramic records where nonpersonal metadata is confirmed.

## Known failure modes

- Array exceeds maxItems of 32 — request rejected with validation error
- Invalid dataClass value outside enum ['public','synthetic'] — schema validation failure
- nonpersonalMetadata not set to true (const constraint) — request rejected
- Empty or malformed record objects in arrays — parsing error or null comparison result
- Network timeout for large record arrays approaching the 32-item limit

## 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 ceramic lot/method-pinned measurement 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 ceramic measurement record arrays are equivalent in terms of pins, scope, and typed projection content, ignoring field ordering differences. Does not certify the underlying artifact or provide raw-byte equality — it is a supplied-record analysis only.

## 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/ceramic-measurements-export-semantic-parity-00024411/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)