# Tool Schemas Declared-Bound Audit

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

Audits declared tool-schema request/response byte ceilings against caller-specified limits, reporting compliance without executing real traffic.

## Facts

- Endpoint: POST https://www.mahastrategies.com/api/v1/verify/tool-schemas/declared-bound-audit?utm_source=zero.xyz
- Price: $0.010106/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-28
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/tool-schemas-declared-bound-audit-07867155
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_eA9hcytxtoCRYY-nqhKZ8

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 tool-schemas-declared-bound-audit-07867155 -d '<json body>'
```

Example prompt: Audit these 5 tool schema contracts for me — they should be classified as public data, with a maximum request size of 8192 bytes, maximum response size of 16384 bytes, and maximum total response bytes of 65536. Flag anything that exceeds those declared ceilings.

## When to prefer this

Use this endpoint when you need a lightweight, offline compliance check of declared tool-schema byte limits without executing real API calls or measuring live traffic. Ideal for CI/CD pipelines, pre-deployment gates, or auditing tool catalogs against organizational size policies. Prefer this over live traffic monitoring when you only need to validate declarations and want fast, stateless results with no side effects.

## Known failure modes

- Empty or missing contracts array returns validation error
- contracts array exceeding 32 items is rejected
- nonpersonalMetadata must be exactly true or request is rejected
- dataClass must be 'public' or 'synthetic' or request fails
- byte ceiling values exceeding 1,000,000 are rejected
- Payment failure via x402 results in 402 response and no audit performed

## How this service works

Compare declared tool-schema declaration request/response byte ceilings with caller limits, including total declared response bytes. Values are declarations, not real traffic or measured costs. Offline typed nonpersonal metadata only. Result retention: 24 hours; minimal receipt metadata: 90 days.

## Output

Returns a comparison of each submitted tool schema contract's declared request/response byte ceilings against the caller-specified limits, including total declared response bytes. Identifies which contracts exceed specified bounds. Results are retained for 24 hours; minimal receipt metadata is kept for 90 days. No real traffic is measured; all values are declarations only.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "contracts": {
   "type": "array",
   "maxItems": 32,
   "minItems": 1
  },
  "dataClass": {
   "enum": [
    "public",
    "synthetic"
   ],
   "type": "string"
  },
  "maximumRequestBytes": {
   "type": "integer",
   "maximum": 1000000,
   "minimum": 0
  },
  "nonpersonalMetadata": {
   "type": "boolean",
   "const": true
  },
  "maximumResponseBytes": {
   "type": "integer",
   "maximum": 1000000,
   "minimum": 0
  },
  "maximumTotalResponseBytes": {
   "type": "integer",
   "maximum": 1000000,
   "minimum": 0
  }
 }
}
```

## More

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