# Identity Records - Export Semantic Parity

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

Compares two sets of parsed typed identity record projections for semantic equivalence, preserving pins and scope while ignoring ordering differences

## Facts

- Endpoint: POST https://www.mahastrategies.com/api/v1/verify/identity-records/export-semantic-parity?utm_source=zero.xyz
- Price: $0.039306/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-16
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/identity-records-export-semantic-parity-569b88f4
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_ew5OXe3UVbIFfKNcO_5Qu

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 identity-records-export-semantic-parity-569b88f4 -d '<json body>'
```

Example prompt: Compare these two sets of public nonpersonal identity record projections — up to 32 records each in the before and after arrays — and tell me if they're semantically equivalent, ignoring any ordering differences but preserving all pins and scope.

## When to prefer this

Use this endpoint when you need to verify that two ordered-different but semantically equivalent sets of typed nonpersonal identity record projections are consistent — for example after a pipeline transformation, a sort operation, or a schema migration. This is not suitable for live identity resolution, signature verification, person identification, DID resolution, or revocation checks. Prefer this over raw byte-equality checks when order independence is required but pin and scope fidelity must be guaranteed.

## Known failure modes

- Arrays exceed 32 items — returns validation error
- dataClass not set to 'public' or 'synthetic' — returns enum validation error
- nonpersonal metadata flag not set to true — rejected as required constant
- Malformed or unparseable record projections — returns parse error
- Mismatched schema versions between before and after arrays — may produce false negatives
- Service unavailable — returns 5xx error

## 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 public nonpersonal agent credential declarations. No DID resolution, live revocation lookup, signature verification, person identification, key custody or identity certification. Offline typed nonpersonal metadata only. Result retention: 24 hours; minimal receipt metadata: 90 days.

## Output

Returns a semantic parity assessment indicating whether the before and after typed record projections are equivalent, detailing any pin preservation failures, scope mismatches, or ordering-independent content differences. Results are retained for 24 hours; minimal receipt metadata is retained for 90 days.

## 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/identity-records-export-semantic-parity-569b88f4/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)