# Publication Records - Export Semantic Parity

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

Compares two sets of parsed bibliographic record projections for semantic parity, preserving pins and scope while ignoring field order, without asserting raw-byte equality or independent artifact certification.

## Facts

- Endpoint: POST https://www.mahastrategies.com/api/v1/intel/publication-records/export-semantic-parity?utm_source=zero.xyz
- Price: $0.039332/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-25
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/publication-records-export-semantic-parity-81f3d259
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_1dx5bEChVne-ggt5BUMHk

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 publication-records-export-semantic-parity-81f3d259 -d '<json body>'
```

Example prompt: Compare these two sets of publication record projections — up to 10 records in the 'before' array and 10 in the 'after' array — and tell me if they're semantically equivalent, using only public data and ignoring field order but preserving all pins and scope.

## When to prefer this

Choose this endpoint when you need to semantically compare two snapshots of bibliographic record projections — such as before and after an update — where field ordering is irrelevant but pins and scope must be preserved. It is appropriate for publisher, DOI, work, or edition-level record quality control workflows. It is not appropriate when you need byte-level equality, independent artifact certification, or live publication lookup.

## Known failure modes

- Arrays exceed 32-item maximum causing validation error
- dataClass value not in allowed enum ('public' or 'synthetic')
- nonpersonalMetadata not set to true (const constraint violation)
- Malformed record objects in before/after arrays causing parse failure
- Empty or mismatched record structures yielding inconclusive parity result
- Payment failure or insufficient USDC balance blocking the request

## How this service works

Compare parsed typed record projections, preserving all pins and scope while ignoring order; not raw-byte equality or proof of the underlying artifact for publisher/work/DOI/edition-pinned bibliographic Supplied-record analysis, not independent certification. Full contract at the free describe URL.

## Output

Returns a semantic parity assessment between the 'before' and 'after' bibliographic record projection arrays, indicating whether they are equivalent under order-agnostic comparison while preserving all declared pins and scope. Does not provide raw-byte equality checks or independent artifact certification.

## 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/publication-records-export-semantic-parity-81f3d259/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)