# Market Catalogues Declared-Bound Audit

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

Compares canonical integer minor-unit strings using BigInt against a single caller-declared inclusive bound within the same record, source, revision, currency, and scale context.

## Facts

- Endpoint: POST https://www.mahastrategies.com/api/v1/intel/market-catalogues/declared-bound-audit?utm_source=zero.xyz
- Price: $0.010172/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-16
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/market-catalogues-declared-bound-audit-2743bee3
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_UQm6qgs-y4iWrKqLg7se1

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 market-catalogues-declared-bound-audit-2743bee3 -d '<json body>'
```

Example prompt: Can you audit these market catalogue measurement records against their declared inclusive bound — I have up to 20 measurements and the bound is in the same record — treat the data as synthetic and confirm nonpersonal metadata is true?

## When to prefer this

Choose this endpoint when you need to audit integer minor-unit values (e.g. currency amounts in cents) against a single caller-declared inclusive bound within the same record context, using BigInt-safe comparison. It is specifically suited for market catalogue data integrity checks where bounds are declared inline with the measurement record rather than derived from an external reference. Not a substitute for independent certification or multi-bound range checking.

## Known failure modes

- Mismatched array lengths between bounds and measurements returns a validation error
- Non-integer or non-canonical string values cause parsing failures
- Exceeding maxItems (32) for either array returns a schema validation error
- Missing required nonpersonalMetadata: true field causes rejection
- Invalid dataClass value outside 'public' or 'synthetic' enum causes rejection

## How this service works

Compare exact canonical integer minor-unit strings using BigInt against one inclusive caller-declared bound in the same record/source/revision/currency/scale Supplied-record analysis, not independent certification. Full contract at the free describe URL.

## Output

Returns a per-record analysis of whether each canonical integer minor-unit string satisfies the declared inclusive bound within the same record, source, revision, currency, and scale context — including pass/fail status and details of any violations. 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/market-catalogues-declared-bound-audit-2743bee3/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)