# Ephemeris Snapshots - Required Field Coverage

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

Checks which required fields are present or missing in supplied ephemeris snapshot records (target, centre, frame, time-scale, correction, kernel pins, etc.) without independently certifying their validity.

## Facts

- Endpoint: POST https://www.mahastrategies.com/api/v1/celestial/ephemeris-snapshots/required-field-coverage?utm_source=zero.xyz
- Price: $0.010155/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-required-field-coverage-8cdcc85b
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_aiIAksLGVdUwY0-lFUaZQ

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-required-field-coverage-8cdcc85b -d '<json body>'
```

Example prompt: Check these 10 public ephemeris snapshot rows and tell me which of the required fields — target, centre, frame, time-scale, correction, and kernel — are missing or null in any of the records.

## When to prefer this

Choose this endpoint when you need a lightweight, fast check for field presence/absence in ephemeris snapshot records — specifically when you do not need independent value certification, only coverage analysis. Prefer this over full validation pipelines when dealing with up to 32 public or synthetic ephemeris rows and needing a rapid gap report on scientific dataset fields like target, centre, frame, time-scale, correction, or kernel pins.

## Known failure modes

- Missing or empty 'rows' array returns a validation error
- 'requiredFields' array outside 1–8 items rejected
- 'rows' array exceeding 32 items rejected
- 'nonpersonalMetadata' not set to true causes rejection
- Invalid 'dataClass' value (not 'public' or 'synthetic') returns enum error
- Malformed row objects may result in incomplete analysis or error response
- Payment failure (x402) blocks the request entirely

## How this service works

Check presence of required scientific dataset/method/revision/content pins; null is missing, not an invalid credential or artifact 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 per-row (and/or aggregate) analysis indicating which required fields are present and which are null or missing across the submitted ephemeris snapshot records. Does not certify validity of field values — only confirms presence or absence.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "rows": {
   "type": "array",
   "maxItems": 32,
   "minItems": 1
  },
  "dataClass": {
   "enum": [
    "public",
    "synthetic"
   ],
   "type": "string"
  },
  "requiredFields": {
   "type": "array",
   "maxItems": 8,
   "minItems": 1
  },
  "nonpersonalMetadata": {
   "type": "boolean",
   "const": true
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/ephemeris-snapshots-required-field-coverage-8cdcc85b/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)