# Orbital Records Scope Boundary Audit

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

Validates that orbital record rows conform to declared owner, subject, revision, and allowed scope labels, enforcing exact boundary constraints without granting access permissions.

## Facts

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

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 orbital-records-scope-boundary-audit-47cc1d25 -d '<json body>'
```

Example prompt: Can you audit these 5 orbital record rows for owner 'AstroCorpXY', subject 'sat-001', revision 'v2.3', data class 'synthetic', with allowed scopes ['read','analyze'] to check they stay within declared scope boundaries — nonpersonalMetadata is true?

## When to prefer this

Choose this endpoint when you need to enforce declared scope label boundaries on a batch of orbital records (up to 32 rows) and verify that owner, subject, and revision references are exactly matched. It is suited for governance workflows where you need an audit trail of scope conformance rather than independent certification. Prefer this over general data validation endpoints when the data is specifically orbital/celestial record metadata subject to scope label constraints and non-personal data requirements.

## Known failure modes

- Missing required fields (ownerRef, subjectRef, revision, allowedScopes, rows) return validation errors
- Rows array below 1 or above 32 items returns out-of-range error
- allowedScopes array below 1 or above 16 items returns constraint error
- dataClass must be 'public' or 'synthetic'; other values return enum rejection
- nonpersonalMetadata must be boolean true; false or missing may cause rejection
- Malformed row objects may return row-level parse errors
- Payment failure or insufficient USDC balance returns 402 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/solution-pinned orbital Supplied-record analysis, not independent certification. Full contract at the free describe URL.

## Output

Returns a structured audit report indicating whether each supplied orbital record row conforms to the declared owner, subject, revision, and scope label constraints. Reports which rows match or violate allowed scope labels, without granting any access permissions for the underlying orbital data. Does not perform independent certification.

## 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/orbital-records-scope-boundary-audit-47cc1d25/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)