# Sky Observations Record Sequence Diff

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

Computes the difference between two ordered lists of sky observation records, separating true insertions and deletions from reordering of surviving records.

## Facts

- Endpoint: POST https://www.mahastrategies.com/api/v1/celestial/sky-observations/record-sequence-diff?utm_source=zero.xyz
- Price: $0.035236/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-16
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/sky-observations-record-sequence-diff-7c3cdd55
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_LNEBRZ8yP8ty3gS_qUZAb

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 sky-observations-record-sequence-diff-7c3cdd55 -d '<json body>'
```

Example prompt: I have two snapshots of sky observation records — the before list has 10 entries and the after list has 12 — both using public data class. Can you diff them and tell me which records were genuinely inserted or deleted versus which ones just got reordered?

## When to prefer this

Choose this endpoint when you need to cleanly separate record-level insertions and deletions from positional reordering within sky observation sequences, especially when surviving record order must remain stable and you want to audit changes without conflating the two types of mutation. It is suited for supplied-record analysis (not independent certification) against a pinned sky frame, epoch, observer, and method context.

## Known failure modes

- Arrays exceeding 32 items each will be rejected
- Missing or invalid dataClass enum value causes validation error
- nonpersonalMetadata must be explicitly set to true or request is rejected
- Malformed array elements may cause processing errors
- Empty before and after arrays return a no-change result

## How this service works

Separate record changes from shared-record reordering; inserting or deleting a record does not itself reorder surviving records for sky frame/epoch/observer/method-pinned Supplied-record analysis, not independent certification. Full contract at the free describe URL.

## Output

Returns a structured diff of the two record arrays that distinguishes genuine insertions and deletions from reordering of surviving records, scoped to the supplied frame/epoch/observer/method pins, without independently certifying the underlying observation data.

## 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/sky-observations-record-sequence-diff-7c3cdd55/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)