# Ephemeris Snapshots - Scope Boundary Audit

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

Audits supplied ephemeris snapshot records against declared owner, subject, revision, and allowed scope labels to verify exact boundary compliance without granting any access or permission.

## Facts

- Endpoint: POST https://www.mahastrategies.com/api/v1/celestial/ephemeris-snapshots/scope-boundary-audit?utm_source=zero.xyz
- Price: $0.038329/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-scope-boundary-audit-9db06cb7
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_aU2x5I9Ssc1HhJsf4m1Ah

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-scope-boundary-audit-9db06cb7 -d '<json body>'
```

Example prompt: Audit these 5 ephemeris snapshot records for owner 'astro-org-42', subject 'mars-orbit-2024', revision 'v3.1', with allowed scopes ['public','synthetic'], and nonpersonalMetadata set to true — check that every record's scope labels fall within the declared boundary.

## When to prefer this

Choose this endpoint when you need to audit supplied ephemeris snapshot records for exact scope boundary compliance against declared owner, subject, revision, and allowed scope labels — particularly for celestial/astronomical data governance workflows. It is a record-analysis tool (not an independent certification service), so prefer it when you already have the records and need to verify they conform to pre-declared scope constraints rather than fetching or generating ephemeris data.

## Known failure modes

- Missing required fields (ownerRef, subjectRef, revision, allowedScopes) result in validation error
- rows array outside 1–32 item bounds returns schema error
- dataClass value outside ['public','synthetic'] enum causes rejection
- nonpersonalMetadata not set to true (const) causes request failure
- Mismatched ownerRef or subjectRef not found in supplied rows may return no-match audit result
- Malformed revision string may cause parsing error

## How this service works

Enforce exact declared owner, subject, revision and allowed scope labels; a matching label grants no permission or access 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 an audit report indicating whether each supplied ephemeris snapshot row's scope labels match the declared owner, subject, revision, and allowed scope list — highlighting any boundary violations without granting permissions or certifying the data independently.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "rows": {
   "type": "array",
   "maxItems": 32,
   "minItems": 1
  },
  "ownerRef": {
   "type": "string"
  },
  "revision": {
   "type": "string"
  },
  "dataClass": {
   "enum": [
    "public",
    "synthetic"
   ],
   "type": "string"
  },
  "subjectRef": {
   "type": "string"
  },
  "allowedScopes": {
   "type": "array",
   "maxItems": 16,
   "minItems": 1
  },
  "nonpersonalMetadata": {
   "type": "boolean",
   "const": true
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/ephemeris-snapshots-scope-boundary-audit-9db06cb7/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)