# Bibliographies Export Semantic Parity

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

Compares two sets of parsed bibliography records for semantic equivalence, preserving pins and scope while ignoring record order.

## Facts

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

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

Example prompt: Check whether these two bibliography export sets are semantically equivalent — I have up to 20 records in the before state and 18 records in the after state, using public data class, and I want to confirm all pins and scope are preserved even if the order changed.

## When to prefer this

Choose this endpoint when you need to determine whether two sets of bibliography records are semantically identical after operations like reordering, migration, or transformation — specifically when pin preservation (corpus, work, style, revision) and scope integrity matter but byte-level or ordering differences are irrelevant. Use it for supplied-record analysis rather than independent artifact certification.

## Known failure modes

- Before or after arrays exceed 32 items — request rejected
- dataClass value outside 'public' or 'synthetic' enum — validation error
- nonpersonalMetadata not set to true — schema const violation
- Empty or malformed record objects in arrays — parse error
- Mismatched pin structure causing false non-parity — ambiguous result

## 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 corpus/work/style/revision-pinned bibliography Supplied-record analysis, not independent certification. Full contract at the free describe URL.

## Output

Returns a semantic parity assessment indicating whether the before and after bibliography record sets are equivalent, confirming that all pins (corpus, work, style, revision) and scope boundaries are preserved, while disregarding record ordering differences. Does not perform raw-byte comparison or independently certify the underlying artifact.

## 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/bibliographies-export-semantic-parity-b6763660/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)