# Campaign Disclosures Declared-Bound Audit

> Campaign Disclosures Declared-Bound Audit is a paid API for AI agents from www.mahastrategies.com, paid per call via x402, $0.01017/call, status unknown (last checked 2026-10-16).

Validates integer minor-unit campaign disclosure values against a caller-declared inclusive bound using BigInt comparison, operating only on supplied record data without independent certification.

## Facts

- Endpoint: POST https://www.mahastrategies.com/api/v1/intel/campaign-disclosures/declared-bound-audit?utm_source=zero.xyz
- Price: $0.01017/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-16
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/campaign-disclosures-declared-bound-audit-66da874f
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_wiKhuw2czfcCXjGRrOSwM

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-declared-bound-audit-66da874f -d '<json body>'
```

Example prompt: Can you audit these campaign disclosure records against our declared bound of 250000 minor units — the data class is public and there are up to 10 records to check — and tell me which ones fail the inclusive bound comparison?

## When to prefer this

Use this endpoint when you need exact, BigInt-precise comparison of campaign disclosure integer amounts against caller-declared inclusive bounds, particularly when floating-point imprecision is unacceptable for minor-unit financial figures. Prefer this over generic numeric validators when the domain is campaign finance disclosures and you need to validate up to 32 records in a single call with public or synthetic data class semantics.

## Known failure modes

- Non-integer or improperly formatted minor-unit string causes parsing failure
- Bounds array length exceeds maxItems of 32
- Measurements array is empty or exceeds 32 items
- dataClass enum value is not 'public' or 'synthetic'
- nonpersonalMetadata is not exactly true (const constraint violation)
- Mismatched array lengths between bounds and measurements
- Network timeout on large batch inputs

## How this service works

Compare exact canonical integer minor-unit strings using BigInt against one inclusive caller-declared bound in the same record/source/revision/currency/scale Supplied-record analysis, not independent certification. Full contract at the free describe URL.

## Output

Returns per-record audit outcomes indicating whether each supplied integer minor-unit campaign disclosure value satisfies the caller-declared inclusive bound, using exact BigInt comparison. Results are scoped strictly to the supplied records and declared bounds; no independent certification is provided.

## Request schema (JSON Schema)

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

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/campaign-disclosures-declared-bound-audit-66da874f/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)