# Telescope Calibrations – Reference Integrity Map

> Telescope Calibrations – Reference Integrity Map is a paid API for AI agents from www.mahastrategies.com, paid per call via x402, $0.035251/call, status unknown (last checked 2026-10-16).

Checks parent existence and detects cycles within owner and subject hierarchies in supplied telescope calibration records.

## Facts

- Endpoint: POST https://www.mahastrategies.com/api/v1/celestial/telescope-calibrations/reference-integrity-map?utm_source=zero.xyz
- Price: $0.035251/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-reference-integrity-map-8b90bbad
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_f4eSVoh50sl4HloXsYhqk

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-reference-integrity-map-8b90bbad -d '<json body>'
```

Example prompt: Can you check these telescope calibration records for broken parent references or cycles in the owner and subject hierarchy? I have up to 20 rows of public-class calibration data with non-personal metadata only.

## When to prefer this

Choose this endpoint when you need to validate parent-child reference integrity and detect cycles specifically within telescope calibration record sets, particularly when working with public or synthetic data classes that carry non-personal metadata. Prefer this over generic graph cycle detectors when your data is framed as telescope calibration rows and you need structured integrity reporting in that domain context.

## Known failure modes

- Empty or oversized rows array (must be 1–32 items) returns validation error
- dataClass value outside 'public' or 'synthetic' enum causes rejection
- nonpersonalMetadata not set to true causes request failure
- Malformed row objects may cause partial or failed analysis
- Service unavailability returns HTTP error with no integrity map

## How this service works

Check parent existence and cycles within owner and subject Supplied-record analysis, not independent certification. Full contract at the free describe URL.

## Output

Returns a reference integrity map identifying which rows have missing parent references, which form cycles within owner or subject hierarchies, and which pass validation — scoped to the supplied records only, not an independent external certification.

## Request schema (JSON Schema)

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

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/telescope-calibrations-reference-integrity-map-8b90bbad/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)