# Technical Manuals Schema Directionality Checker

> Technical Manuals Schema Directionality Checker is a paid API for AI agents from www.mahastrategies.com, paid per call via x402, $0.035037/call, status unknown (last checked 2026-10-15).

Compares before/after sets of technical manual extraction fields to detect type, requiredness, and nullability changes for ingestion compatibility checking.

## Facts

- Endpoint: POST https://www.mahastrategies.com/api/v1/context/technical-manuals/schema-directionality?utm_source=zero.xyz
- Price: $0.035037/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-15
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/technical-manuals-schema-directionality-checker-c5619b7f
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap__YESC9LE7Ql-V__iEO6RR

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 technical-manuals-schema-directionality-checker-c5619b7f -d '<json body>'
```

Example prompt: Can you check whether my updated technical manual extraction schema is still ingestion-compatible with the old one? The before set has these 5 field definitions and the after set has 7 — data class is public, and this is nonpersonal metadata only.

## When to prefer this

Choose this endpoint when you need a lightweight, offline check of declared field-level schema changes (type, requiredness, nullability) between two versions of a technical manual extraction schema. Prefer it over full schema subtyping tools when you only care about ingestion compatibility of nonpersonal, public or synthetic metadata. Not suitable for checking instruction correctness, semantic meaning changes, or personal data schemas.

## Known failure modes

- before array is empty or missing — requires at least 1 item
- after or before arrays exceed 32 items — request rejected
- dataClass set to a value outside 'public' or 'synthetic' enum — validation error
- nonpersonalMetadata not set to true — rejected as personal data not accepted
- malformed field definitions in before/after arrays — parsing error returned
- network timeout for large field sets near the 32-item limit

## How this service works

Compare closed manual extraction fields for type, requiredness and nullability changes. Checks declared ingestion compatibility only, not full schema subtyping or instruction correctness. Offline typed nonpersonal metadata only. Result retention: 24 hours; minimal receipt metadata: 90 days.

## Output

A structured report listing which fields changed in type, requiredness, or nullability between the before and after schema sets, flagging directional compatibility issues for ingestion pipelines. Does not perform full schema subtyping or instruction correctness validation. Results are retained for 24 hours; minimal receipt metadata is kept for 90 days.

## 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
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/technical-manuals-schema-directionality-checker-c5619b7f/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)