# Sky Observations - Revision Delta Map

> Sky Observations - Revision Delta Map is a paid API for AI agents from www.mahastrategies.com, paid per call via x402, $0.021327/call, status unknown (last checked 2026-10-20).

Compares two revisions of sky observation records to enumerate changes in owner, subject, revision, content, and scope pin fields by stable record ID.

## Facts

- Endpoint: POST https://www.mahastrategies.com/api/v1/celestial/sky-observations/revision-delta-map?utm_source=zero.xyz
- Price: $0.021327/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-20
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/sky-observations-revision-delta-map-ce226c5e
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_SF-9WfJSGJuqGbNVZorX0

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

Example prompt: Show me the delta map between my two sets of sky observation records — I have up to 32 records in the before snapshot and 32 in the after snapshot, using public data class, and I only need non-personal metadata changes enumerated by field: owner, subject, revision, content pin, and scope pin.

## When to prefer this

Choose this endpoint when you need field-level change detection between two specific revision snapshots of sky observation records pinned to frame, epoch, observer, or method, and where you require stable record-ID-keyed output. It is not an independent certification service — use it when the supplied record snapshots already exist and you need structured diff output for auditing or consistency checking.

## Known failure modes

- Array exceeds 32-item limit — request rejected
- dataClass value not in enum ['public','synthetic'] — validation error
- nonpersonalMetadata not set to true (const) — schema rejection
- Empty before and after arrays return empty delta map
- Mismatched or unknown record IDs may result in missing entries in the delta map

## How this service works

Enumerate owner, subject, revision, content and scope pin changes by stable record ID in two supplied revisions for sky frame/epoch/observer/method-pinned Supplied-record analysis, not independent certification. Full contract at the free describe URL.

## Output

Returns a structured delta map keyed by stable record ID listing field-level changes (owner, subject, revision, content pin, scope pin) detected between the supplied before and after revision arrays, scoped to the specified data class and non-personal metadata constraint.

## 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-revision-delta-map-ce226c5e/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)