# Telescope Calibrations Schema Directionality

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

Compares closed export-field supplied-record analysis for telescope calibration schema directionality, returning a structured schema analysis without independent certification.

## Facts

- Endpoint: POST https://www.mahastrategies.com/api/v1/celestial/telescope-calibrations/schema-directionality?utm_source=zero.xyz
- Price: $0.035253/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-schema-directionality-6461d836
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_m0u6mEe63iraBqgAWVZnj

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-schema-directionality-6461d836 -d '<json body>'
```

Example prompt: Compare my telescope calibration schema fields — the before set has up to 20 entries and the after set has 15 entries — using public data class, with nonpersonal metadata only, and tell me if the schema directionality is consistent.

## When to prefer this

Use this endpoint when you need a fast, inspectable comparison of telescope calibration schema field sets before and after a change, particularly for closed export-field records using public or synthetic data classes. Prefer this over general schema validators when the domain is specifically telescope calibration data and directionality analysis is the required output.

## Known failure modes

- Empty or missing 'before' array (minItems:1 required) returns validation error
- 'after' array exceeding 32 items returns schema violation
- Invalid 'dataClass' value outside 'public' or 'synthetic' enum returns rejection
- nonpersonalMetadata not set to true (const constraint violated) returns error
- Malformed JSON body returns 400-level error

## How this service works

Compare closed export-field Supplied-record analysis, not independent certification. Full contract at the free describe URL.

## Output

Returns a structured analysis of schema directionality for the supplied before and after export-field arrays, identifying consistency or discrepancies in the closed export-field records. Does not provide independent certification — results reflect supplied-record comparison only.

## Request schema (JSON Schema)

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

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/telescope-calibrations-schema-directionality-6461d836/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)