# Campaign Disclosures - Required Field Coverage Check

> Campaign Disclosures - Required Field Coverage Check is a paid API for AI agents from www.mahastrategies.com, paid per call via x402, $0.010169/call, status unknown (last checked 2026-11-04).

Checks whether required issuer/subject or producer/work pins are present in campaign disclosure filing records for a given committee, form, period, or revision

## Facts

- Endpoint: POST https://www.mahastrategies.com/api/v1/intel/campaign-disclosures/required-field-coverage?utm_source=zero.xyz
- Price: $0.010169/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-required-field-coverage-check-6c089a16
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_2p3rcuYyaBIL5rRxlnuST

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-required-field-coverage-check-6c089a16 -d '<json body>'
```

Example prompt: Check whether the required issuer and subject pins are present in these campaign disclosure records — treat the data as public, and validate against the required fields: 'committee_id', 'form_type', 'period', and 'filer_id'. Here are the rows to check.

## When to prefer this

Use this endpoint when you need to programmatically verify that specific required disclosure field pins (issuer, subject, producer, work, committee, form, period, revision) are non-null in a batch of campaign finance filing records. Prefer this over manual review or generic schema validators when working with public campaign disclosure data and need structured coverage analysis tied to specific field names.

## Known failure modes

- Missing required 'rows' array returns validation error
- 'rows' array exceeding 32 items is rejected
- 'requiredFields' array exceeding 8 items is rejected
- 'nonpersonalMetadata' must be boolean true or request fails
- Invalid 'dataClass' enum value returns schema error
- Empty 'requiredFields' array below minimum of 1 rejected
- Malformed row objects may return null coverage rather than error

## How this service works

Check presence of required issuer/subject or producer/work pins; null is missing, not an invalid credential or artifact for committee/form/period/revision-pinned public filing Supplied-record analysis, not independent certification. Full contract at the free describe URL.

## Output

Returns a per-row or aggregate analysis indicating which required field pins are present (non-null) and which are missing (null), covering the specified required fields across the submitted rows. Does not certify credentials or independently validate filing authenticity — reports only presence or absence of declared pins.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "rows": {
   "type": "array",
   "maxItems": 32,
   "minItems": 1
  },
  "dataClass": {
   "enum": [
    "public",
    "synthetic"
   ],
   "type": "string"
  },
  "requiredFields": {
   "type": "array",
   "maxItems": 8,
   "minItems": 1
  },
  "nonpersonalMetadata": {
   "type": "boolean",
   "const": true
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/campaign-disclosures-required-field-coverage-check-6c089a16/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)