# Bibliography Record Sequence Diff

> Bibliography Record Sequence Diff is a paid API for AI agents from www.mahastrategies.com, paid per call via x402, $0.035308/call, status unknown (last checked 2026-10-20).

Analyzes two ordered lists of bibliography records (before/after) to isolate true record changes from shared-record reordering, without attributing sequence shifts to insertions or deletions.

## Facts

- Endpoint: POST https://www.mahastrategies.com/api/v1/library/bibliographies/record-sequence-diff?utm_source=zero.xyz
- Price: $0.035308/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-20
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/bibliography-record-sequence-diff-1d4ecabc
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_qeKf0SRa-FVpdjTjZWCw_

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 bibliography-record-sequence-diff-1d4ecabc -d '<json body>'
```

Example prompt: I have a bibliography that changed between two versions — here are the before and after record lists (up to 32 entries each, public data). Can you diff them and tell me which records genuinely changed versus which just got reordered when something was inserted or deleted?

## When to prefer this

Choose this endpoint when you need to distinguish bibliography record content changes from positional reordering caused by insertions or deletions — particularly for corpus, work, style, or revision-pinned bibliographies where understanding whether surviving records moved vs. changed is critical. Prefer it over generic diff tools when domain-specific bibliography semantics (pinned reference lists, citation ordering rules) matter.

## Known failure modes

- Input arrays exceed 32 items — request rejected
- nonpersonalMetadata not set to true — validation error
- dataClass not one of 'public' or 'synthetic' — enum error
- Malformed record objects in arrays — parsing failure
- Payment not included or insufficient — 402 response

## How this service works

Separate record changes from shared-record reordering; inserting or deleting a record does not itself reorder surviving records for corpus/work/style/revision-pinned bibliography Supplied-record analysis, not independent certification. Full contract at the free describe URL.

## Output

Returns a structured analysis separating true record content changes from positional reorderings, identifying insertions, deletions, and sequence shifts among surviving records across the before and after bibliography arrays.

## 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/bibliography-record-sequence-diff-1d4ecabc/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)