# Tool Schemas - Export Semantic Parity

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

Compares two sets of parsed tool-schema declaration exports to verify semantic parity, preserving owner, revision, schema pair, and scope labels while ignoring ordering differences.

## Facts

- Endpoint: POST https://www.mahastrategies.com/api/v1/verify/tool-schemas/export-semantic-parity?utm_source=zero.xyz
- Price: $0.039304/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-29
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/tool-schemas-export-semantic-parity-04313024
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_r4JRhPGa2Crij2xOlm-M2

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

Example prompt: Can you check whether these two sets of tool-schema exports are semantically equivalent — compare the before and after snapshots using public data class, making sure owner, revision, schema pairs, and scope labels all match even if their order is different?

## When to prefer this

Choose this endpoint when you need a strict, offline, order-insensitive semantic comparison of tool-schema declaration exports — specifically when you care about preserving owner, revision, schema pair, and scope label fidelity without any runtime interpretation or coercion. Prefer it over generic diff tools when the domain is typed nonpersonal metadata and you need an auditable, receipt-generating parity check.

## Known failure modes

- Input arrays exceed 32 items per set — request rejected
- nonpersonalMetadata not set to true — validation error
- dataClass value outside 'public' or 'synthetic' enum — schema validation failure
- Malformed schema declaration entries in before/after arrays — parsing error
- Service unavailable — 5xx response

## How this service works

Compare parsed tool-schema declaration 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

Returns a structured comparison result indicating whether the two sets of tool-schema declaration exports are semantically equivalent, listing any differences in owner, revision, schema pair, or scope label assignments, while ignoring ordering. Result is 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/tool-schemas-export-semantic-parity-04313024/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)