# Api Contracts - Export Semantic Parity

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

Compares two sets of parsed HTTP API contract exports for semantic parity, preserving owner, revision, schema pair, target, and scope labels while ignoring order differences.

## Facts

- Endpoint: POST https://www.mahastrategies.com/api/v1/verify/api-contracts/export-semantic-parity?utm_source=zero.xyz
- Price: $0.039303/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-20
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/api-contracts-export-semantic-parity-b141ab6c
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_6obLO1bSXjk0sS3tlc-mM

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

Example prompt: Can you check whether these two API contract exports are semantically equivalent — the before set has our v1.2 contracts and the after set has v1.3, both marked as public data — and tell me if the owner, revision, schema pairs, targets, and scope labels all match up regardless of field ordering?

## When to prefer this

Choose this endpoint when you need to verify semantic equivalence between two snapshots of parsed HTTP API contract exports — specifically preserving owner, revision, schema pair, target, and scope label fidelity while being agnostic to field ordering. Prefer this over generic diff tools when you need typed, offline, nonpersonal metadata comparison without runtime inference or arbitrary schema interpretation, especially in governance, versioning, or CI/CD contexts.

## Known failure modes

- Array exceeds 32-item limit — request rejected with validation error
- nonpersonalMetadata not set to true — request rejected
- dataClass not one of 'public' or 'synthetic' — invalid enum error
- Malformed contract objects in before/after arrays — parsing failure
- Result unavailable after 24-hour retention window
- Service unavailable or 402 payment required if USDC payment not provided

## How this service works

Compare parsed HTTP contract exports preserving owner, revision, schema pair, exact target and scope labels while ignoring order. No arbitrary schema interpretation or runtime parity is inferred. Offline typed nonpersonal metadata only. Result retention: 24 hours; minimal receipt metadata: 90 days.

## Output

A structured comparison result indicating whether the before and after sets of parsed HTTP contract exports are semantically equivalent, with details on whether owner, revision, schema pairs, target labels, and scope labels match exactly, independent of ordering. 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/api-contracts-export-semantic-parity-b141ab6c/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)