# Sky Observations Scope Boundary Audit

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

Validates that a set of sky observation records conform to declared owner, subject, revision, and allowed scope labels, ensuring no unauthorized scope permissions are implicitly granted.

## Facts

- Endpoint: POST https://www.mahastrategies.com/api/v1/celestial/sky-observations/scope-boundary-audit?utm_source=zero.xyz
- Price: $0.038327/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-16
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/sky-observations-scope-boundary-audit-affdae2a
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_64VvlEVxPeeEcqn_qgfni

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

Example prompt: Audit these 12 sky observation rows for scope boundary compliance — the ownerRef is 'org-solar-42', subjectRef is 'target-epoch-7', revision is 'v3', dataClass is 'synthetic', allowedScopes are ['read','inspect'], and nonpersonalMetadata is true.

## When to prefer this

Choose this endpoint when you need to enforce declared scope boundary rules on a batch of sky observation records and verify that matching scope labels do not inadvertently grant permissions. Prefer this over general validation services when the data involves pinned celestial frame, epoch, observer, or method references and you need explicit owner/subject/revision binding checked against an allowedScopes list without independent certification.

## Known failure modes

- Missing required ownerRef or subjectRef causes validation rejection
- Rows array exceeding 32 items returns a schema validation error
- allowedScopes exceeding 16 entries rejected at schema level
- nonpersonalMetadata not set to true (const constraint) causes request failure
- Unrecognized dataClass value outside 'public' or 'synthetic' enum causes error
- Empty rows array (below minItems:1) returns a bad request error

## How this service works

Enforce exact declared owner, subject, revision and allowed scope labels; a matching label grants no permission or access for sky frame/epoch/observer/method-pinned Supplied-record analysis, not independent certification. Full contract at the free describe URL.

## Output

Returns a structured audit report indicating whether each supplied observation row conforms to the declared ownerRef, subjectRef, revision, dataClass, and allowedScopes. Highlights any scope label matches that do not constitute permission grants, and flags records that violate declared boundary constraints without certifying them 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/sky-observations-scope-boundary-audit-affdae2a/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)