# Alloy Measurements Declared Bound Audit

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

Validates whether alloy measurement values fall within caller-supplied quantity/unit bounds within a declared dataset/subject/run/method/revision frame, treating null and censored values as unknown.

## Facts

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

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

Example prompt: Can you audit these 10 alloy tensile strength measurements against my declared bounds — the lower bound is 200 MPa and upper bound is 450 MPa — for dataset 'batch-7', subject 'steel-grade-A', run 3, using public data class? Treat any null or censored values as unknown, not zero.

## When to prefer this

Choose this endpoint when you need to programmatically audit a batch of alloy measurements against explicit caller-defined quantity/unit bounds within a precise dataset/subject/run/method/revision context. It is best suited for materials science data pipelines, lab QA workflows, or simulation checks on synthetic alloy data where null and censored values must be tracked as unknown. Do not use it as a substitute for certified safety or clinical threshold assessments.

## Known failure modes

- Measurements array exceeds 32 items — request rejected
- Bounds array is empty or exceeds 32 items — validation error
- Invalid dataClass value (must be 'public' or 'synthetic') — enum error
- nonpersonalMetadata not set to true — required const field missing
- Mismatched units between measurements and bounds may produce unexpected comparisons
- Censored or null values returned as unknown status, not numerical results
- Payment failure via x402 protocol — endpoint returns 402

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

## Output

Returns a structured audit result for each measurement indicating whether it falls within the inclusive caller-supplied bounds, flags measurements that are out of range, and marks null or censored values as unknown rather than zero. Results are scoped to the exact dataset/subject/run/method/revision frame provided. Does not constitute clinical or safety 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/alloy-measurements-declared-bound-audit-de5914ec/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)