# Telescope Calibrations - Scope Boundary Audit

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

Validates that supplied telescope calibration records conform to declared owner, subject, revision, and allowed scope labels without granting any permissions or independent certification.

## Facts

- Endpoint: POST https://www.mahastrategies.com/api/v1/celestial/telescope-calibrations/scope-boundary-audit?utm_source=zero.xyz
- Price: $0.03833/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-16
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/telescope-calibrations-scope-boundary-audit-d9bf8db2
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_MIy-4LFh2H3lbLPo_iB-s

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

Example prompt: Audit these 5 telescope calibration records for owner 'obs-team-alpha', subject 'detector-7B', revision 'r2024.3', with allowed scopes ['filter','binning','readout'], dataClass 'synthetic', and nonpersonalMetadata set to true — flag any rows that fall outside the declared scope boundaries.

## When to prefer this

Use this endpoint when you need to enforce declared scope label boundaries on a batch of telescope calibration records and verify that owner, subject, and revision declarations are consistent — particularly for data quality control pipelines processing synthetic or public calibration datasets. Prefer it over general metadata validators when the specific domain is telescope/instrument calibration and the concern is scope label conformance rather than scientific accuracy.

## Known failure modes

- Missing required fields (ownerRef, subjectRef, revision, allowedScopes) result in validation error
- rows array outside 1–32 item bounds returns schema rejection
- allowedScopes exceeding 16 items returns schema rejection
- nonpersonalMetadata not explicitly set to true causes rejection
- Invalid dataClass value outside ['public','synthetic'] enum fails validation
- Malformed or empty row objects may produce incomplete audit results

## How this service works

Enforce exact declared owner, subject, revision and allowed scope labels; a matching label grants no permission or access for instrument/detector/filter/binning/readout/pipeline-pinned calibration Supplied-record analysis, not independent certification. Full contract at the free describe URL.

## Output

Returns a per-row analysis of whether each supplied calibration record conforms to the declared owner, subject, revision, and allowed scope labels. Highlights records with scope boundary violations or label mismatches. Does not grant permissions or serve as independent certification — purely a supplied-record conformance report.

## 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/telescope-calibrations-scope-boundary-audit-d9bf8db2/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)