# Grant Records Schema Directionality Analyzer

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

Compares before/after export field sets for grant records to determine schema directionality and closed-field analysis

## Facts

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

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 grant-records-schema-directionality-analyzer-9e110319 -d '<json body>'
```

Example prompt: Compare these two grant record export field sets for schema directionality — before fields are ['id','title','amount'] and after fields are ['id','title','amount','status'], using public data class and non-personal metadata only.

## When to prefer this

Use this endpoint when you need to formally compare two versions of a grant records export schema to determine the direction and nature of field changes, particularly in compliance or audit workflows where closed-field export validation is required. Prefer this over generic diff tools when dealing specifically with grant record data governed by non-personal metadata constraints.

## Known failure modes

- before array missing or empty (minItems:1 required)
- after array exceeds 32 items or before array exceeds 32 items
- invalid dataClass value outside of 'public' or 'synthetic' enum
- nonpersonalMetadata not set to true (const:true enforced)
- malformed array elements in before/after fields
- payment authorization failure via x402 protocol

## How this service works

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

## Output

Returns a schema directionality comparison report indicating which export fields were added, removed, or unchanged between the before and after field arrays, along with analysis of whether the schema change is valid given the declared data class and metadata constraints.

## 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/grant-records-schema-directionality-analyzer-9e110319/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)