# Tabular Records - Export Semantic Parity

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

Compares parsed pinned tabular row projections between two snapshots by matching primary keys, table/revision frames, and content digests — without relying on row order or ingestion IDs.

## Facts

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

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 tabular-records-export-semantic-parity-4a40f225 -d '<json body>'
```

Example prompt: Compare these two tabular record snapshots — before has up to 32 rows and after has up to 32 rows, both classified as 'public' data — and tell me if the primary keys, table/revision frames, and content digests all match semantically, regardless of row order.

## When to prefer this

Choose this endpoint when you need to verify semantic equivalence of two tabular dataset snapshots without exposing raw cell contents — ideal for post-migration audits, ETL regression checks, and export pipeline validation where row order cannot be guaranteed and only digest-level comparison is acceptable. Prefer it over full diff tools when privacy constraints require nonpersonal metadata handling, or when you only need to confirm identity rather than enumerate changes.

## Known failure modes

- Row arrays exceeding 32 items rejected with validation error
- Non-boolean or absent nonpersonalMetadata field causes rejection
- dataClass value outside 'public' or 'synthetic' enum rejected
- Mismatched schema structure in row objects causes parse failure
- Timeout if row digest computation takes too long
- Stale results unavailable after 24-hour retention window

## How this service works

Compare parsed pinned tabular row projections without relying on row order or ingestion IDs. Primary keys, table/revision frames and content digests must match; this does not compare unseen cell contents. Offline typed nonpersonal metadata only. Result retention: 24 hours; minimal receipt metadata: 90 days.

## Output

Returns a parity assessment indicating whether the before and after row sets match on primary keys, table/revision frames, and content digests. Highlights any mismatches found. Does not expose unseen cell contents. Result retained for 24 hours; minimal receipt metadata 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/tabular-records-export-semantic-parity-4a40f225/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)