# Ephemeris Snapshots - Unit-Label Consistency Audit

> Ephemeris Snapshots - Unit-Label Consistency Audit is a paid API for AI agents from www.mahastrategies.com, paid per call via x402, $0.012329/call, status unknown (last checked 2026-10-20).

Audits quantity and unit label consistency within a supplied ephemeris or celestial measurement frame, checking coordinate, clock, model, and calibration labels against each other.

## Facts

- Endpoint: POST https://www.mahastrategies.com/api/v1/celestial/ephemeris-snapshots/unit-label-consistency?utm_source=zero.xyz
- Price: $0.012329/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-unit-label-consistency-audit-6215a7af
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap___BsUMXXjAKZ30JfCpnGi

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-unit-label-consistency-audit-6215a7af -d '<json body>'
```

Example prompt: Can you audit the unit and quantity label consistency in these ephemeris measurements I'm supplying? They're public-class data with no personal metadata — I want to know if there are any coordinate, clock, or calibration label mismatches in the frame.

## When to prefer this

Choose this endpoint when you need to audit internal unit and quantity label consistency within a supplied ephemeris or celestial measurement frame — especially for coordinate, clock, model, or calibration labels. It is appropriate for public or synthetic data classes and is distinct from full certification services. Prefer it over general data validation tools when the domain is specifically ephemeris or celestial data and label-level consistency is the concern.

## Known failure modes

- Invalid or unsupported dataClass enum value returns a validation error
- Supplying more than 32 measurements exceeds the maxItems limit and is rejected
- Missing or false nonpersonalMetadata const field causes request rejection
- Malformed measurements array structure results in a parse error
- Empty measurements array (below minItems of 1) is rejected

## How this service works

Audit quantity/unit labels in the exact supplied frame, including coordinate/clock or model/calibration Supplied-record analysis, not independent certification. Full contract at the free describe URL.

## Output

Returns an audit report indicating whether the quantity and unit labels within the supplied ephemeris measurements are consistent, flagging any mismatches in coordinate, clock, model, or calibration labels. The analysis is scoped to the supplied frame and does not constitute independent certification.

## Request schema (JSON Schema)

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

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/ephemeris-snapshots-unit-label-consistency-audit-6215a7af/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)
