# Ephemeris Snapshots - Revision Delta Map

> Ephemeris Snapshots - Revision Delta Map is a paid API for AI agents from www.mahastrategies.com, paid per call via x402, $0.021329/call, status unknown (last checked 2026-11-05).

Compares two revisions of a pinned ephemeris record and enumerates changes in owner, subject, revision, content, and scope pins by stable record ID.

## Facts

- Endpoint: POST https://www.mahastrategies.com/api/v1/celestial/ephemeris-snapshots/revision-delta-map?utm_source=zero.xyz
- Price: $0.021329/call
- Payment: x402
- Status: unknown
- Last checked: 2026-11-05
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/ephemeris-snapshots-revision-delta-map-ae8d5802
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_msnFuCLBfQyPv8AtON7SP

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-revision-delta-map-ae8d5802 -d '<json body>'
```

Example prompt: Show me what changed between the before and after snapshots for our pinned ephemeris records — I want to see any owner, subject, content, or scope pin changes for public data.

## When to prefer this

Use this endpoint when you need a structured, record-level diff of two pinned ephemeris snapshot revisions and want to enumerate specific field-level changes (owner, subject, content, scope) by stable ID. Prefer this over general versioning tools when working specifically with target/centre/frame/time-scale/correction/kernel-pinned ephemeris data.

## Known failure modes

- Array exceeds maxItems of 32 — request rejected with validation error
- dataClass enum value not recognized — invalid input error
- nonpersonalMetadata not set to true — contract violation
- Empty or mismatched revision arrays yielding no delta — empty result set
- Kernel or frame pin mismatch between revisions causing incomplete comparison

## How this service works

Enumerate owner, subject, revision, content and scope pin changes by stable record ID in two supplied revisions for target/centre/frame/time-scale/correction/kernel-pinned ephemeris Supplied-record analysis, not independent certification. Full contract at the free describe URL.

## Output

A structured map keyed by stable record ID listing enumerated changes in owner, subject, revision, content, and scope pins between the two supplied revision arrays — limited to supplied-record analysis, not 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/ephemeris-snapshots-revision-delta-map-ae8d5802/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)