# Edition Records - Declared-Bound Audit

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

Validates that declared nonnegative integer aggregate counts for edition records fall within caller-supplied inclusive bounds, checking across source, subject, snapshot, and unit dimensions.

## Facts

- Endpoint: POST https://www.mahastrategies.com/api/v1/library/edition-records/declared-bound-audit?utm_source=zero.xyz
- Price: $0.01018/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-20
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/edition-records-declared-bound-audit-7e744d60
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_h_VXh6oaJgSops2mNKPhF

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 edition-records-declared-bound-audit-7e744d60 -d '<json body>'
```

Example prompt: Can you audit these edition record counts against our declared bounds — we have 5 measurements and 5 bounds for public data, and I need to confirm every count stays within its inclusive limit across all sources, subjects, snapshots, and units?

## When to prefer this

Choose this endpoint when you need a lightweight, per-call audit to confirm that declared nonnegative integer aggregate counts for edition records stay within caller-supplied inclusive bounds, without needing to download or process the underlying text. It is suitable for data quality pipelines that must enforce count caps across source, subject, snapshot, and unit dimensions on public or synthetic nonpersonal library edition metadata.

## Known failure modes

- Mismatched array lengths between bounds and measurements returns a validation error
- Values outside nonnegative integer range are rejected
- Exceeding maxItems (32) for bounds or measurements array causes request rejection
- Missing required nonpersonalMetadata:true field causes rejection
- Invalid dataClass value outside enum ['public','synthetic'] causes rejection
- Malformed input schema returns 400-level error

## 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 structured comparison of each supplied measurement against its corresponding inclusive bound, indicating whether each nonnegative integer aggregate count passes or fails the declared limit, broken down by source, subject, snapshot, and unit dimensions. No independent certification is provided — results reflect analysis of caller-supplied records only.

## 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/edition-records-declared-bound-audit-7e744d60/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)