# Grant Records - Export Semantic Parity

> Grant Records - Export Semantic Parity is a paid API for AI agents from www.mahastrategies.com, paid per call via x402, $0.039334/call, status unknown (last checked 2026-10-25).

Compares two sets of parsed, typed grant record projections for semantic parity, preserving all pins and scope while ignoring field order.

## Facts

- Endpoint: POST https://www.mahastrategies.com/api/v1/intel/grant-records/export-semantic-parity?utm_source=zero.xyz
- Price: $0.039334/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-25
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/grant-records-export-semantic-parity-918559ca
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_reJSKq4AZ8SqGbFIB8VxV

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-export-semantic-parity-918559ca -d '<json body>'
```

Example prompt: Compare these two sets of grant record projections — up to 32 entries each in the before and after arrays — using public data class and nonpersonal metadata only, and tell me if they're semantically equivalent ignoring field order.

## When to prefer this

Choose this endpoint when you need to verify that two sets of parsed grant record projections are semantically equivalent across typed pins and scope, especially after a data transformation, migration, or export pipeline — and where field order differences are acceptable but pin-level content equivalence is required. Prefer this over raw-byte comparison tools when order-agnostic semantic matching is the goal, and over general data diff tools when grant-specific pin semantics (agency, opportunity, program, jurisdiction, revision) matter.

## Known failure modes

- Array exceeds 32 item limit — request rejected with validation error
- dataClass value not in ['public','synthetic'] enum — schema validation failure
- nonpersonalMetadata not set to true (const) — request rejected
- Malformed or untyped record projections — comparison cannot be performed
- Empty or mismatched projection formats — partial or null parity result returned

## How this service works

Compare parsed typed record projections, preserving all pins and scope while ignoring order; not raw-byte equality or proof of the underlying artifact for agency/opportunity/program/jurisdiction/revision-pinned grant Supplied-record analysis, not independent certification. Full contract at the free describe URL.

## Output

Returns a structured semantic parity report indicating whether the before and after typed grant record projections are equivalent, including details on any mismatched pins, scope discrepancies, or ordering-agnostic differences across agency, opportunity, program, jurisdiction, and revision pins. Does not certify the underlying artifact or provide raw-byte equality.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "after": {
   "type": "array",
   "maxItems": 32,
   "minItems": 0
  },
  "before": {
   "type": "array",
   "maxItems": 32,
   "minItems": 0
  },
  "dataClass": {
   "enum": [
    "public",
    "synthetic"
   ],
   "type": "string"
  },
  "nonpersonalMetadata": {
   "type": "boolean",
   "const": true
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/grant-records-export-semantic-parity-918559ca/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)