# Publication Records Schema Directionality Analyzer

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

Compares 'before' and 'after' export-field declarations in publication records to analyze schema directionality and flag field-level mismatches or additions.

## Facts

- Endpoint: POST https://www.mahastrategies.com/api/v1/intel/publication-records/schema-directionality?utm_source=zero.xyz
- Price: $0.035265/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-16
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/publication-records-schema-directionality-analyzer-0268695f
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_uNlSHP5Rmjf66Humen15c

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 publication-records-schema-directionality-analyzer-0268695f -d '<json body>'
```

Example prompt: Compare these two publication record schemas for me — the 'before' list has fields ['title','author','doi'] and the 'after' list has ['title','author','doi','abstract'], with dataClass set to 'public' and nonpersonalMetadata confirmed true; I want to see which export fields were added or changed and whether the directionality looks valid.

## When to prefer this

Choose this endpoint when you need a fast, structured comparison of export-field declarations between two versions of a publication record schema, specifically to detect directionality shifts (additions, removals, reordering) in public or synthetic datasets where nonpersonal metadata is confirmed. It is a supplied-record analysis tool, not an independent certification service, so prefer it for internal pipeline auditing and pre-publish validation rather than regulatory compliance attestation.

## Known failure modes

- Empty 'before' array (minItems:1 violated) returns validation error
- 'after' or 'before' arrays exceeding 32 items return schema rejection
- Invalid dataClass value outside ['public','synthetic'] enum causes 400 error
- nonpersonalMetadata not set to true (const:true) causes rejection
- Malformed array items in before/after fields may return parse errors
- Network timeout on the POST endpoint returns no result

## 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 between 'before' and 'after' field arrays, identifying added, removed, or reordered export fields, flagging mismatches against closed-field declarations, and noting compatibility issues for consumers who disallow extra fields. Results reflect supplied-record analysis only, not independent certification.

## 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/publication-records-schema-directionality-analyzer-0268695f/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)