# Protein Measurements Declared-Bound Audit

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

Audits declared protein measurement records by comparing finite values against caller-supplied inclusive quantity/unit bounds within a specific 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/protein-measurements/declared-bound-audit?utm_source=zero.xyz
- Price: $0.010126/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-20
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/protein-measurements-declared-bound-audit-b13c46c8
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_kW0k2J8_wdF8kDvaF-ZyZ

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

Example prompt: Can you audit these 12 protein measurement records from our synthetic dataset against inclusive bounds of 0.5–10.0 mg/mL, treating any null or censored values as unknown rather than zero?

## When to prefer this

Choose this endpoint when you need to audit declared protein measurement records against specific caller-supplied inclusive bounds within a precise dataset/subject/run/method/revision frame, and you need null and censored values treated as unknown rather than zero. Prefer this over generic range-checking tools when the domain is specifically proteomics or protein assay data and you need formal audit semantics rather than simple filtering.

## Known failure modes

- Invalid or empty measurements array (minItems:1 not met)
- Bounds array exceeds maxItems:32 limit
- Measurements array exceeds maxItems:32 limit
- dataClass not one of 'public' or 'synthetic'
- nonpersonalMetadata not set to true (const constraint)
- Malformed quantity/unit pairs in bounds
- Mixed or incompatible units between measurements and bounds
- Payment failure via x402 protocol

## 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 protein measurement Supplied-record analysis, not independent certification. Full contract at the free describe URL.

## Output

Returns a per-record audit result indicating whether each finite protein measurement falls within the caller-supplied inclusive quantity/unit bounds, with null and censored values flagged as unknown (not zero). Results are scoped to the exact dataset/subject/run/method/revision frame provided and do not constitute clinical or safety certifications.

## 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/protein-measurements-declared-bound-audit-b13c46c8/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)