# Grant Records - Record Sequence Diff

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

Compares two ordered lists of grant records to identify insertions, deletions, content changes, and reorderings, while keeping these change types analytically separate.

## Facts

- Endpoint: POST https://www.mahastrategies.com/api/v1/intel/grant-records/record-sequence-diff?utm_source=zero.xyz
- Price: $0.035278/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-record-sequence-diff-bdf369cd
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_MfiEZ1ME0fZxALr6F3_Sh

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-record-sequence-diff-bdf369cd -d '<json body>'
```

Example prompt: Compare these two lists of grant records — the before list has 12 entries and the after list has 14 entries, both marked as public data — and tell me which records were actually added or deleted versus which surviving records just got reordered.

## When to prefer this

Use this endpoint when you need to precisely distinguish between grant record insertions/deletions and positional reordering of surviving records — a distinction most generic diff tools collapse. Ideal for auditing grant record sequences pinned to agency, opportunity, program, jurisdiction, or revision dimensions where understanding sequence stability separately from content changes is analytically important. Best for public or synthetic data up to 32 records per snapshot.

## Known failure modes

- Array exceeds 32-item maximum — request rejected
- nonpersonalMetadata must be exactly true — omitting or setting false causes validation failure
- Invalid dataClass value outside 'public' or 'synthetic' enum — rejected
- Malformed record objects in before/after arrays — unparseable diff
- Empty or null arrays on one or both sides — may return trivial all-added or all-removed result
- Payment failure via x402 protocol — endpoint not reached

## How this service works

Separate record changes from shared-record reordering; inserting or deleting a record does not itself reorder surviving records 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 diff separating the before and after record arrays into distinct categories: records added, records removed, records with content changes, and records that were reordered (position changed without content change). Critically, insertions and deletions do not themselves count as reorderings of surviving records.

## 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-record-sequence-diff-bdf369cd/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)