# Scientific Dataset Records - Record Sequence Diff

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

Compares two snapshots of scientific dataset records to identify insertions and deletions, keeping record reordering separate from actual record changes.

## Facts

- Endpoint: POST https://www.mahastrategies.com/api/v1/intel/scientific-dataset-records/record-sequence-diff?utm_source=zero.xyz
- Price: $0.035302/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-25
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/scientific-dataset-records-record-sequence-diff-f344f565
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_P8rorH7WLG0Wvmdhkio9_

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 scientific-dataset-records-record-sequence-diff-f344f565 -d '<json body>'
```

Example prompt: I have two snapshots of scientific dataset records — the before list and the after list, both public data — and I want to know exactly which records were inserted or deleted without conflating that with any reordering of surviving records.

## When to prefer this

Choose this endpoint when you need to isolate true record insertions and deletions from reordering noise between two dataset snapshots — specifically for scientific datasets with public or synthetic data classification. Prefer it when you need a clean, manifest-pinned diff that does not conflate surviving-record reordering with actual record changes, and when you are working within the 32-record-per-snapshot constraint.

## Known failure modes

- before or after array exceeds 32 items — request rejected
- dataClass not one of 'public' or 'synthetic' — validation error
- nonpersonalMetadata not set to true — request rejected
- malformed or empty arrays cause ambiguous diff output
- network timeout on large or complex record payloads

## How this service works

Separate record changes from shared-record reordering; inserting or deleting a record does not itself reorder surviving records for repository/dataset/schema/method/revision-pinned manifest Supplied-record analysis, not independent certification. Full contract at the free describe URL.

## Output

Returns a structured diff of the two record arrays indicating which records were inserted and which were deleted, explicitly separating these changes from any reordering of surviving records, scoped to the supplied record arrays without independent 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/scientific-dataset-records-record-sequence-diff-f344f565/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)