# Campaign Disclosures - Record Sequence Diff

> Campaign Disclosures - Record Sequence Diff is a paid API for AI agents from www.mahastrategies.com, paid per call via x402, $0.03529/call, status unknown (last checked 2026-11-04).

Separates genuine record insertions/deletions from positional reordering in campaign disclosure filings, analyzing before/after record arrays without touching surviving-record order.

## Facts

- Endpoint: POST https://www.mahastrategies.com/api/v1/intel/campaign-disclosures/record-sequence-diff?utm_source=zero.xyz
- Price: $0.03529/call
- Payment: x402
- Status: unknown
- Last checked: 2026-11-04
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/campaign-disclosures-record-sequence-diff-79f3b853
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_q5eb2zz27G8Hm64CGwPNy

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 campaign-disclosures-record-sequence-diff-79f3b853 -d '<json body>'
```

Example prompt: Can you diff these two versions of a campaign disclosure record set — one with 12 records and one with 14 — and tell me which records were actually inserted or deleted versus which surviving records just got reordered? Use public data class.

## When to prefer this

Use this endpoint when you need to precisely distinguish whether changes between two versions of a campaign disclosure record set represent true additions/removals versus mere positional reordering of unchanged records — particularly when auditing amended filings, validating revision history, or building compliance workflows that must not conflate record identity changes with sequence changes.

## Known failure modes

- Array exceeds 32-item limit returns validation error
- Missing nonpersonalMetadata:true flag may cause rejection
- Invalid dataClass value outside 'public'/'synthetic' enum fails schema validation
- Empty before and after arrays with no changes yields trivial diff result
- Malformed record objects in input arrays may produce incomplete analysis

## How this service works

Separate record changes from shared-record reordering; inserting or deleting a record does not itself reorder surviving records for committee/form/period/revision-pinned public filing Supplied-record analysis, not independent certification. Full contract at the free describe URL.

## Output

A structured analysis distinguishing genuine record insertions and deletions from positional reordering of surviving records within the same committee/form/period/revision scope, without independently certifying the underlying data.

## 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/campaign-disclosures-record-sequence-diff-79f3b853/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)