# Thermal Measurements Declared-Bound Audit

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

Validates caller-supplied thermal measurement values against declared quantity/unit bounds within a specific dataset/subject/run/method/revision frame, flagging out-of-bound, null, and censored values.

## Facts

- Endpoint: POST https://www.mahastrategies.com/api/v1/compute/thermal-measurements/declared-bound-audit?utm_source=zero.xyz
- Price: $0.010146/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-20
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/thermal-measurements-declared-bound-audit-a6af4bab
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_ZcROd1aIKzclTjP9PsfD4

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 thermal-measurements-declared-bound-audit-a6af4bab -d '<json body>'
```

Example prompt: Check my public thermal measurement dataset — I have up to 20 readings from run #3, method revision 2 — and verify each one falls within my declared bounds of 20–95 degrees Celsius; flag anything null, censored, or out of range.

## When to prefer this

Use this endpoint when you need to audit a specific set of thermal measurements against caller-declared inclusive bounds within a precise scientific framing (dataset/subject/run/method/revision), and you want explicit handling of null and censored values as unknowns rather than zeros. Prefer this over generic range-check tools when the audit must be scoped to public or synthetic data classes and non-personal metadata is a compliance requirement.

## Known failure modes

- Missing required 'nonpersonalMetadata: true' field causes rejection
- Bounds array or measurements array exceeding 32 items returns an error
- Mismatched units between measurements and bounds may produce unexpected audit results
- Invalid dataClass value (not 'public' or 'synthetic') causes schema validation failure
- Empty bounds or measurements arrays (below minItems: 1) are rejected

## How this service works

Compare finite measurements with inclusive caller-supplied quantity/unit bounds in the exact dataset/subject/run/method/revision frame; null and censored values are unknown, not zero; thresholds are not clinical or safety limits for thermal export Supplied-record analysis, not independent certification. Full contract at the free describe URL.

## Output

Returns a per-measurement audit report indicating whether each thermal value falls within the caller-declared inclusive bounds, along with flags for null values (treated as unknown, not zero), censored values, and out-of-bound readings, all scoped to the specified dataset/subject/run/method/revision frame. No independent certification is provided.

## 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/thermal-measurements-declared-bound-audit-a6af4bab/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)