# Reading Plans - Declared-Bound Aggregate Count Audit

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

Validates that exact nonnegative integer aggregate counts from reading plan records fall within a caller-supplied inclusive upper bound, across specified sources, subjects, snapshots, and units.

## Facts

- Endpoint: POST https://www.mahastrategies.com/api/v1/library/reading-plans/declared-bound-audit?utm_source=zero.xyz
- Price: $0.010178/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-16
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/reading-plans-declared-bound-aggregate-count-audit-1f117495
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_zGPFhdmZOpwIKh71c2JuC

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 reading-plans-declared-bound-aggregate-count-audit-1f117495 -d '<json body>'
```

Example prompt: Check whether the reading plan aggregate counts for these 3 measurements stay within a bound of 500, using public data class with nonpersonal metadata only.

## When to prefer this

Choose this endpoint when you need to programmatically verify that declared aggregate count totals from reading plan records do not exceed a specific inclusive numeric ceiling, particularly when working with public or synthetic library data and requiring nonpersonal metadata compliance. It is appropriate when the validation is based on caller-supplied records rather than independent data retrieval or certification.

## Known failure modes

- Bounds array empty or exceeds 32 items — request rejected
- Measurements array empty or exceeds 32 items — request rejected
- dataClass not one of 'public' or 'synthetic' — validation error
- nonpersonalMetadata not explicitly set to true — request rejected
- Aggregate count in supplied record is negative or non-integer — processing error
- Mismatch between number of bounds and measurements — ambiguous comparison result

## How this service works

Compare exact nonnegative integer aggregate counts with one inclusive caller-supplied bound matching every source, subject, snapshot and unit Supplied-record analysis, not independent certification. Full contract at the free describe URL.

## Output

Returns a pass/fail or compliance result indicating whether each measurement's nonnegative integer aggregate count satisfies the caller-supplied inclusive upper bound, covering the exact declared source, subject, snapshot, and unit. Results are based on supplied records only, not independent certification.

## 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/reading-plans-declared-bound-aggregate-count-audit-1f117495/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)