# Identity Records - Declared Bound Audit

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

Validates that declared nonnegative measurement counts do not exceed a caller-specified ceiling, for offline nonpersonal public or synthetic metadata only.

## Facts

- Endpoint: POST https://www.mahastrategies.com/api/v1/verify/identity-records/declared-bound-audit?utm_source=zero.xyz
- Price: $0.01011/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-25
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/identity-records-declared-bound-audit-e0025db3
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_RiA048qJSZj1Vd5q0PBJ3

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

Example prompt: Check whether these 10 declared public nonpersonal metadata measurements all fall under a ceiling of 5000 seconds — flag any that exceed the bound.

## When to prefer this

Choose this endpoint when you need a lightweight, offline, policy-level check that a set of declared nonpersonal public or synthetic metadata counts does not exceed a caller-configured ceiling. It is not appropriate for live identity resolution, DID lookup, cryptographic signature verification, person identification, key custody, or legally binding quota enforcement — use it strictly for auditing declared measurement counts against a numeric bound.

## Known failure modes

- Measurements array is empty or exceeds 32 items — rejected with validation error
- Maximum value out of allowed range (0 to 1,000,000,000) — schema validation failure
- Unit not in allowed enum (seconds/milliseconds) — rejected
- dataClass not in allowed enum (public/synthetic) — rejected
- nonpersonalMetadata not set to true — request rejected
- Malformed integer values in measurements array — validation error

## How this service works

Compare nonnegative declared counts against an explicit ceiling in matching units. Bounds are caller policy, not security strength, material safety or legally binding quotas for public nonpersonal agent credential declarations. No DID resolution, live revocation lookup, signature verification, person identification, key custody or identity certification. Offline typed nonpersonal metadata only. Result retention: 24 hours; minimal receipt metadata: 90 days.

## Output

Returns a compliance result indicating whether all supplied measurements fall within the declared ceiling in the specified unit, including which measurements (if any) exceed the bound, along with minimal receipt metadata retained for 90 days and full results available for 24 hours.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "unit": {
   "enum": [
    "seconds",
    "milliseconds"
   ],
   "type": "string"
  },
  "maximum": {
   "type": "integer",
   "maximum": 1000000000,
   "minimum": 0
  },
  "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/identity-records-declared-bound-audit-e0025db3/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)