# Ephemeris Snapshots - Record Sequence Diff

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

Compares two snapshots of ephemeris records to isolate true insertions and deletions from shared-record reordering across target, centre, frame, time-scale, correction, and kernel-pinned dimensions.

## Facts

- Endpoint: POST https://www.mahastrategies.com/api/v1/celestial/ephemeris-snapshots/record-sequence-diff?utm_source=zero.xyz
- Price: $0.035248/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-20
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/ephemeris-snapshots-record-sequence-diff-ef3d69dc
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_5b0Mdzr2vhOiYn6VoSASC

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 ephemeris-snapshots-record-sequence-diff-ef3d69dc -d '<json body>'
```

Example prompt: I have two lists of ephemeris records — a before snapshot with up to 30 entries and an after snapshot with 28 entries, both public data. Can you diff them to tell me which records were genuinely inserted or deleted versus just reordered among the surviving ones?

## When to prefer this

Choose this endpoint when you need to cleanly separate genuine ephemeris record insertions and deletions from positional reordering of surviving records across two snapshots. It is specifically designed for kernel-pinned, time-scale, frame, and correction-aware ephemeris data — not general-purpose list diffing. Use it when your ephemeris pipeline produces before/after snapshots and you must audit structural changes without conflating sequence shuffling with true record additions or removals.

## Known failure modes

- Array exceeds maxItems limit of 32 — reduce snapshot size
- Missing or invalid dataClass enum value ('public' or 'synthetic' required)
- nonpersonalMetadata not set to true (const:true constraint violated)
- Empty before and after arrays produce trivially empty diff
- Malformed record entries in arrays cause parsing failure
- Ambiguous record identity fields may cause incorrect insert/delete attribution

## How this service works

Separate record changes from shared-record reordering; inserting or deleting a record does not itself reorder surviving records for target/centre/frame/time-scale/correction/kernel-pinned ephemeris Supplied-record analysis, not independent certification. Full contract at the free describe URL.

## Output

Returns a structured diff indicating which records in the 'after' snapshot are true insertions (not present in 'before'), which records were deleted (present in 'before' but absent in 'after'), and confirming that surviving records were reordered rather than changed — keeping insertions/deletions and reordering as distinct signals.

## 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/ephemeris-snapshots-record-sequence-diff-ef3d69dc/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)