# Publication Records Declared Bound Audit

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

Audits declared nonnegative integer aggregate counts in publication records against caller-supplied inclusive bounds, verifying consistency across source, subject, snapshot, and unit dimensions.

## Facts

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

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

Example prompt: Audit these publication record counts — I have up to 20 measurements from public data and I need to verify each aggregate count falls within the inclusive bounds I'm supplying; flag any that violate the declared limits.

## When to prefer this

Choose this endpoint when you need to audit declared integer aggregate counts in publication records against caller-specified inclusive bounds across multiple dimensions (source, subject, snapshot, unit), particularly for up to 32 measurements at a time. It is best suited for compliance checks on supplied data — not for independent certification or external verification of publication claims.

## Known failure modes

- Bounds array exceeds 32 items — request rejected
- Measurements array is empty or exceeds 32 items — validation error
- nonpersonalMetadata is not set to true — request rejected
- dataClass is not 'public' or 'synthetic' — enum validation error
- Mismatched array lengths between bounds and measurements — error response
- Negative integer values provided — violates nonnegative constraint

## 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 an audit result indicating whether each declared nonnegative integer aggregate count in the publication records satisfies the caller-supplied inclusive bounds, with per-record pass/fail status covering all source, subject, snapshot, and unit dimensions. This is a supplied-record analysis, 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/publication-records-declared-bound-audit-d9846b88/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)