# Ephemeris Snapshots - Schema Directionality

> Ephemeris Snapshots - Schema Directionality is a paid API for AI agents from www.mahastrategies.com, paid per call via x402, $0.035247/call, status unknown (last checked 2026-10-16).

Compares closed export-field directionality in supplied ephemeris snapshot records, reporting field-level analysis without independent certification.

## Facts

- Endpoint: POST https://www.mahastrategies.com/api/v1/celestial/ephemeris-snapshots/schema-directionality?utm_source=zero.xyz
- Price: $0.035247/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-16
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/ephemeris-snapshots-schema-directionality-acf7d270
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_pgm5tqjGwvaYd5iqKl7DF

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-schema-directionality-acf7d270 -d '<json body>'
```

Example prompt: Check the directionality of export fields in these two sets of ephemeris snapshot records — I have up to 10 'before' records and 5 'after' records, data class is 'public', nonpersonal metadata only, and I want to allow extra fields in the comparison.

## When to prefer this

Use this endpoint when you have two sets of ephemeris snapshot records and need to assess how closed export fields have shifted in directionality between them. It is appropriate for schema-level auditing of celestial data exports where you supply both before and after record snapshots. Do not use it expecting independent certification of underlying data accuracy or live ephemeris computation.

## Known failure modes

- 'before' array is empty or missing (minItems:1 violation) — returns validation error
- 'after' array exceeds 32 items or 'before' exceeds 32 items — returns schema violation error
- nonpersonalMetadata not set to true (const:true) — returns constraint failure
- Invalid dataClass value (not 'public' or 'synthetic') — returns enum validation error
- Malformed record objects in before/after arrays — may return partial or error response

## How this service works

Compare closed export-field Supplied-record analysis, not independent certification. Full contract at the free describe URL.

## Output

Returns a structured analysis report of closed export-field directionality differences between the 'before' and 'after' record sets, flagging field-level discrepancies. This is a supplied-record analysis, not independent certification of the underlying data.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "after": {
   "type": "array",
   "maxItems": 32,
   "minItems": 0
  },
  "before": {
   "type": "array",
   "maxItems": 32,
   "minItems": 1
  },
  "dataClass": {
   "enum": [
    "public",
    "synthetic"
   ],
   "type": "string"
  },
  "nonpersonalMetadata": {
   "type": "boolean",
   "const": true
  },
  "consumerAllowsExtraFields": {
   "type": "boolean"
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/ephemeris-snapshots-schema-directionality-acf7d270/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)