# Tool Context - Export Semantic Parity

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

Compares parsed call-context projections across two export snapshots, checking semantic parity while ignoring array order but preserving attempt counts, digest pins, and declared states.

## Facts

- Endpoint: POST https://www.mahastrategies.com/api/v1/context/tool-context/export-semantic-parity?utm_source=zero.xyz
- Price: $0.039299/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-16
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/tool-context-export-semantic-parity-ebfd1541
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_r756Tnr_02oK1RwyuDcg1

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-context-export-semantic-parity-ebfd1541 -d '<json body>'
```

Example prompt: Compare these two tool context export snapshots — before has up to 32 entries, after has up to 32 entries — using synthetic data class, and check whether their semantic parity holds while ignoring array ordering but preserving attempt counts, digest pins, and declared states.

## When to prefer this

Choose this endpoint when you need to compare tool call-context projections across two export snapshots semantically — particularly when array ordering is inconsistent but logical equivalence still needs to be verified. Prefer this over raw diff tools when you specifically want to preserve attempt-count, digest-pin, and declared-state semantics while ignoring superficial ordering differences. Best suited for offline, nonpersonal typed metadata validation pipelines.

## Known failure modes

- Arrays exceeding 32 items will be rejected with a validation error
- nonpersonalMetadata must be set to true — any other value will fail validation
- dataClass must be exactly 'public' or 'synthetic' — other values are rejected
- Empty or malformed projection objects in the before/after arrays may cause comparison errors
- Result data expires after 24 hours and cannot be retrieved after that window

## How this service works

Compare parsed call-context projections across exports, ignoring array order but preserving attempts, digest pins and declared states. No raw arguments or results are compared. Offline typed nonpersonal metadata only. Result retention: 24 hours; minimal receipt metadata: 90 days.

## Output

Returns a semantic parity analysis comparing the before and after call-context projection arrays, highlighting mismatches in attempt counts, digest pins, and declared states while ignoring array element ordering. Raw arguments and results are excluded from comparison. 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/tool-context-export-semantic-parity-ebfd1541/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)