# Campaign Disclosures - Scope Boundary Audit

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

Validates that campaign disclosure records match their declared owner, subject, revision, and allowed scope labels without granting any permission or access.

## Facts

- Endpoint: POST https://www.mahastrategies.com/api/v1/intel/campaign-disclosures/scope-boundary-audit?utm_source=zero.xyz
- Price: $0.038336/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-scope-boundary-audit-8bc7a7a1
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_HdfkkxqggPcO3icQfRNTH

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-scope-boundary-audit-8bc7a7a1 -d '<json body>'
```

Example prompt: Audit these 10 campaign disclosure rows for committee filings under owner 'OWNER-2024-CA-001', subject 'FORM-460', revision 'v3', using public data class, with allowed scopes ['committee','period'] — I want to confirm every record's scope labels match the declared boundaries exactly.

## When to prefer this

Use this endpoint when you need to programmatically verify that a set of campaign disclosure records (up to 32 rows) strictly conforms to a pinned owner/subject/revision/scope frame before downstream processing or reporting. Prefer this over general-purpose validation when your use case involves public campaign filings, committee forms, or period-pinned disclosures and you need exact label boundary enforcement — not authentication or data certification.

## Known failure modes

- Empty or malformed rows array causes validation rejection
- ownerRef or subjectRef missing results in incomplete boundary check
- revision string mismatch returns scope violation for all rows
- allowedScopes array empty or exceeds 16 items triggers schema error
- dataClass not set to 'public' or 'synthetic' causes enum rejection
- nonpersonalMetadata not set to true (const) returns input error

## How this service works

Enforce exact declared owner, subject, revision and allowed scope labels; a matching label grants no permission or access for committee/form/period/revision-pinned public filing Supplied-record analysis, not independent certification. Full contract at the free describe URL.

## Output

Returns a structured audit report indicating whether each supplied disclosure row's scope labels match the declared owner, subject, revision, and allowed scope constraints. Identifies label mismatches, out-of-scope claims, and boundary violations across up to 32 rows per call. Does not certify authenticity or grant permissions — reports only supply-record-level analysis.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "rows": {
   "type": "array",
   "maxItems": 32,
   "minItems": 1
  },
  "ownerRef": {
   "type": "string"
  },
  "revision": {
   "type": "string"
  },
  "dataClass": {
   "enum": [
    "public",
    "synthetic"
   ],
   "type": "string"
  },
  "subjectRef": {
   "type": "string"
  },
  "allowedScopes": {
   "type": "array",
   "maxItems": 16,
   "minItems": 1
  },
  "nonpersonalMetadata": {
   "type": "boolean",
   "const": true
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/campaign-disclosures-scope-boundary-audit-8bc7a7a1/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)