# Package Manifests - Schema Directionality Analysis

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

Compares before/after snapshots of package manifest export-field records to analyze schema directionality and flag changes in closed export field structure.

## Facts

- Endpoint: POST https://www.mahastrategies.com/api/v1/verify/package-manifests/schema-directionality?utm_source=zero.xyz
- Price: $0.035127/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-16
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/package-manifests-schema-directionality-analysis-d7127ecd
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_HJrvvUVvHQTDMPnmYbWxR

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 package-manifests-schema-directionality-analysis-d7127ecd -d '<json body>'
```

Example prompt: Compare these two package manifest snapshots for schema directionality — the before array has my old manifest records and the after array has the updated ones, both as public data class with nonpersonal metadata only, and tell me if any closed export fields have shifted direction or structure.

## When to prefer this

Choose this endpoint when you need to compare two versions of package manifest export-field records specifically for schema directionality analysis — i.e., detecting whether the structural direction of closed export fields has changed between snapshots. Prefer this over general schema diff tools when you need a focused, supply-side (not independent certification) analysis of manifest export field changes within the constraints of public or synthetic data classes and nonpersonal metadata.

## Known failure modes

- before array is empty or missing (minItems:1 not met) — validation error returned
- after or before arrays exceed 32 items — request rejected with schema violation
- dataClass not set to 'public' or 'synthetic' — enum validation failure
- nonpersonalMetadata not set to true (const constraint) — request rejected
- malformed array items in before/after — parsing error
- network timeout on large snapshot comparisons

## 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 manifest snapshots, identifying which closed export fields have changed direction, added, removed, or shifted structure, along with flags for incompatibilities relative to consumer field tolerance settings.

## 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/package-manifests-schema-directionality-analysis-d7127ecd/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)