# Settlement Receipts Export Semantic Parity

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

Compares two arrays of receipt export projections for semantic equivalence, verifying that network, amount, merchant, and result pins match regardless of array order.

## Facts

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

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 settlement-receipts-export-semantic-parity-dc74111a -d '<json body>'
```

Example prompt: Compare these two sets of settlement receipt exports and check if they're semantically equivalent — same network, amount, merchant, and result pins — even if the array order is different. Use synthetic public data class with nonpersonal metadata only.

## When to prefer this

Use this endpoint when you need to verify that two versions of a settlement receipt export are semantically equivalent despite potential reordering, specifically checking network, amount, merchant, and result pins. Prefer this over general diff tools when order-independence and field-level pin matching are required for non-personal, offline metadata. Not suitable when you need ledger synchronization, delivery confirmation, or real-time financial reconciliation.

## Known failure modes

- Array exceeds 32-item limit — request rejected with validation error
- dataClass not set to 'public' or 'synthetic' — enum validation failure
- nonpersonalMetadata not set to true (const constraint) — request rejected
- Malformed array items causing comparison failure
- Empty or mismatched schema structures between before and after arrays

## How this service works

Compare receipt export projections while preserving network, amount, merchant and result pins independently of array order. No financial ledger synchronization or delivery confirmation. Offline typed nonpersonal metadata only. Result retention: 24 hours; minimal receipt metadata: 90 days.

## Output

Returns a semantic parity verdict comparing two receipt export arrays (before and after), indicating whether network, amount, merchant, and result pins are equivalent independent of ordering. Result data is retained for 24 hours; minimal receipt metadata is retained for 90 days. No ledger synchronization or delivery confirmation is performed.

## 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/settlement-receipts-export-semantic-parity-dc74111a/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)