# License Records Schema Directionality Validator

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

Compares closed export-field directionality in supplied license records against expected schema contracts, reporting field-level mismatches.

## Facts

- Endpoint: POST https://www.mahastrategies.com/api/v1/verify/license-records/schema-directionality?utm_source=zero.xyz
- Price: $0.035121/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-16
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/license-records-schema-directionality-validator-d72aeb79
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_H-wjAbqhXYReR1ZYTyilz

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 license-records-schema-directionality-validator-d72aeb79 -d '<json body>'
```

Example prompt: Compare the before and after snapshots of our public license records export — up to 10 entries before and 5 after — with nonpersonalMetadata set to true, and tell me if there are any schema directionality mismatches in the closed export fields.

## When to prefer this

Choose this endpoint when you need to compare field-level schema directionality in license record exports between two snapshots — particularly for closed export-field analysis on public or synthetic data where nonpersonal metadata compliance is required. It is not an independent certification service but a contract-comparison tool suited for schema drift detection in license data pipelines.

## Known failure modes

- Missing or empty 'before' array (minItems:1 violated) 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:true violated) causes request failure
- Malformed JSON body returns parsing error
- Payment not included or insufficient USDC causes 402 response

## 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 comparison report indicating whether the closed export fields in the supplied license record snapshots conform to expected schema directionality, including details on mismatched or shifted fields between the before and after arrays.

## 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/license-records-schema-directionality-validator-d72aeb79/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)