# Planetary Measurements - Record Sequence Diff

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

Computes the difference between two ordered sequences of planetary measurement records, isolating genuine insertions and deletions from reordering of surviving records.

## Facts

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

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 planetary-measurements-record-sequence-diff-c38087be -d '<json body>'
```

Example prompt: I have two lists of planetary measurement records — a before list and an after list, both public data — and I want to know which records were actually inserted or deleted, ignoring any reordering of the ones that survived. Can you run a sequence diff on them?

## When to prefer this

Use this endpoint when you need to distinguish genuine record-level insertions and deletions from position changes caused by reordering, specifically within the planetary measurements domain. It is the right choice when you have a bounded before/after snapshot (up to 32 records each) and need a clean, declarative diff that does not conflate reordering with mutation. Prefer this over generic diff tools when working with structured celestial measurement records that share target/site/convention/time/method pins.

## Known failure modes

- Array exceeds 32-item limit — request rejected
- nonpersonalMetadata not set to true — validation error
- Invalid dataClass value (must be 'public' or 'synthetic') — schema error
- Malformed record objects in before/after arrays — parsing failure
- Network timeout on large payloads near the 32-item boundary

## How this service works

Separate record changes from shared-record reordering; inserting or deleting a record does not itself reorder surviving records for target/site/convention/time/method-pinned planetary Supplied-record analysis, not independent certification. Full contract at the free describe URL.

## Output

Returns a structured diff of the two supplied planetary measurement record arrays, identifying which records are genuine insertions (present in after but not before) and which are genuine deletions (present in before but not after), while explicitly separating these changes from any reordering of records that survived in both snapshots. Does not perform independent certification — results are analysis of the supplied data only.

## 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/planetary-measurements-record-sequence-diff-c38087be/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)