# Spectrometry Records Declared Bound Audit

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

Validates spectrometry measurements against caller-supplied quantity/unit bounds within a fixed dataset/subject/run/method/revision frame, treating null and censored values as unknown rather than zero.

## Facts

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

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 spectrometry-records-declared-bound-audit-002fede7 -d '<json body>'
```

Example prompt: Check whether these 5 spectrometry measurements from our public dataset all fall within the declared bounds — intensity between 0.01 and 2.5 arbitrary units, wavelength between 400 and 700 nm — treating any null readings as unknown, not zero.

## When to prefer this

Choose this endpoint when you need to validate a finite set of spectrometry measurements (up to 32) against caller-defined inclusive quantity/unit bounds in a strictly locked dataset/subject/run/method/revision frame, and you require explicit handling of null and censored values as unknown rather than zero. Not appropriate for clinical or safety threshold enforcement, independent certification, or real-time streaming spectral data.

## Known failure modes

- Measurements array is empty or exceeds 32 items — request rejected
- Bounds array is empty or exceeds 32 items — request rejected
- dataClass value not in allowed enum ('public' or 'synthetic') — validation error
- nonpersonalMetadata not set to true — request rejected
- Mismatched units between measurements and bounds — may produce incorrect comparison
- Null values misinterpreted by caller as zero — documented behavior: nulls are unknown

## 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 spectral axis/intensity export Supplied-record analysis, not independent certification. Full contract at the free describe URL.

## Output

Returns a per-measurement compliance result indicating whether each value falls within the caller-supplied inclusive bounds, flags measurements that are out of range, and reports null or censored values as unknown rather than zero — scoped strictly to the declared dataset/subject/run/method/revision frame.

## 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/spectrometry-records-declared-bound-audit-002fede7/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)