# Procurement Notices – Declared Bound Audit

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

Audits declared integer minor-unit measurement values against a single inclusive caller-declared bound within the same record, verifying whether each measurement satisfies its paired bound using exact BigInt arithmetic.

## Facts

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

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 procurement-notices-declared-bound-audit-e064a924 -d '<json body>'
```

Example prompt: Can you audit these procurement bid amounts — [120000, 95000, 135000] as public data — against the declared inclusive bound of 130000, and tell me which ones violate the limit? Mark it as non-personal metadata.

## When to prefer this

Choose this endpoint when you need exact, BigInt-precision integer comparison of procurement or contract measurement values against a single inclusive caller-declared bound per record, without floating-point rounding risk. It is specifically suited for public or synthetic procurement notice data where exact minor-unit integer arithmetic is required. Prefer this over general validation tools when the audit scope is a single bound per record and the data is non-personal procurement or contract data.

## Known failure modes

- Empty or oversized measurements array (outside 1–32 items) returns validation error
- Measurements or bounds containing non-integer or non-minor-unit values cause rejection
- Missing nonpersonalMetadata: true field causes request rejection
- Unsupported dataClass value outside 'public' or 'synthetic' enum returns error
- Mismatched array lengths between measurements and bounds may cause per-record audit errors
- Service unavailability or payment failure returns HTTP 402 or 5xx

## 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-measurement audit result indicating whether each supplied integer value satisfies the caller-declared inclusive bound, using exact BigInt arithmetic. Results include pass/fail status for each measurement, identification of out-of-bound entries, and a summary of the audit against the single declared bound within the supplied record scope. No independent certification is provided — analysis is based solely on the supplied record data.

## 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/procurement-notices-declared-bound-audit-e064a924/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)