# Market Catalogues Schema Directionality Checker

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

Compares closed export-field contracts in market catalogue records to detect schema directionality issues such as removed fields, type changes, and newly required fields between before and after states.

## Facts

- Endpoint: POST https://www.mahastrategies.com/api/v1/intel/market-catalogues/schema-directionality?utm_source=zero.xyz
- Price: $0.035295/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-16
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/market-catalogues-schema-directionality-checker-ae805a13
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_XjIJhsBWRL0niPUNJC71N

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 market-catalogues-schema-directionality-checker-ae805a13 -d '<json body>'
```

Example prompt: Compare my market catalogue export field contracts to check for breaking schema changes — the before set has up to 10 fields and the after set has 8, using public data class with nonpersonal metadata only, and my consumer does allow extra fields.

## When to prefer this

Choose this endpoint when you need to validate schema directionality specifically for market catalogue export-field contracts, particularly to catch breaking changes such as field removals, type mutations, or new required fields between two schema versions. It is best suited for governance workflows where downstream consumer compatibility must be verified before deploying catalogue schema updates, and where data is restricted to public or synthetic classes with nonpersonal metadata only.

## Known failure modes

- Empty or malformed before/after arrays cause validation errors
- dataClass enum values other than 'public' or 'synthetic' are rejected
- nonpersonalMetadata must be exactly true (const constraint) or request is rejected
- before array requires at least 1 item (minItems:1); empty before arrays are rejected
- before/after arrays exceeding 32 items are rejected
- Mismatched field formats between before and after sets may produce incomplete analysis

## How this service works

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

## Output

A structured report detailing schema directionality findings between the before and after field sets in market catalogue export contracts, including identified field removals, type changes, and newly required fields, along with a compatibility summary indicating whether the schema evolution is safe for downstream consumers.

## 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/market-catalogues-schema-directionality-checker-ae805a13/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)