# Publication Records - Record Sequence Diff

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

Computes the difference between two ordered lists of publication records, isolating true record insertions/deletions from sequence reordering changes.

## Facts

- Endpoint: POST https://www.mahastrategies.com/api/v1/intel/publication-records/record-sequence-diff?utm_source=zero.xyz
- Price: $0.035266/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-20
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/publication-records-record-sequence-diff-3f2ca27f
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_LkqAKh-Yvok_2F6LhNuh2

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-record-sequence-diff-3f2ca27f -d '<json body>'
```

Example prompt: Can you diff these two publication record lists for me — the before list has records A, B, C and the after list has B, D, C — and tell me which records were actually inserted or deleted versus just reordered? Use public data class.

## When to prefer this

Choose this endpoint when you need to cleanly separate record insertion/deletion events from simple reordering of surviving records in a bibliographic or publication context, particularly when working with publisher, work, DOI, or edition-pinned record lists of up to 32 entries. Prefer it over generic diff tools when the distinction between 'record was removed' and 'record was moved' is semantically important for downstream bibliographic integrity checks.

## Known failure modes

- Input arrays exceeding 32 items are rejected
- Missing or invalid dataClass enum value causes validation error
- nonpersonalMetadata must be true (const); any other value is rejected
- Malformed or non-array before/after inputs return schema validation errors
- Ambiguous record identity may produce uncertain diff results if records lack stable identifiers

## How this service works

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

## Output

A structured analysis separating true record insertions and deletions from sequence reordering events, so callers can distinguish whether surviving records were reordered versus whether actual records were added or removed between the before and after states.

## 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-record-sequence-diff-3f2ca27f/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)