# Inspection Tolerance Batch

> Inspection Tolerance Batch is a paid API for AI agents from www.mahastrategies.com, paid per call via x402, $0.01001/call, status unknown (last checked 2026-10-23).

Classify up to 100 declared measurement intervals against tolerances as pass, fail, or hold using integer millimetre values and absolute interval half-widths.

## Facts

- Endpoint: POST https://www.mahastrategies.com/api/v1/verify/inspection/tolerances?utm_source=zero.xyz
- Price: $0.01001/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-23
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/inspection-tolerance-batch-887d3fca
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_ZmGbLmVFz62VRWM_gccuK

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 inspection-tolerance-batch-887d3fca -d '<json body>'
```

Example prompt: I have 50 dimensional measurements in millimetres with their tolerance half-widths — can you batch classify all of them as pass, fail, or hold against the declared tolerances? The data is public.

## When to prefer this

Choose this endpoint when you need to classify multiple (up to 100) dimensional measurements against tolerances in a single call, working exclusively in integer millimetres with absolute uncertainty half-widths. It is ideal for automated quality control pipelines, pre-shipment audits, or prototype screening where pass/fail/hold classification is needed without sensor verification or engineering approval workflows. Not suitable if you need sensor-verified results, engineering sign-off, or sub-millimetre precision.

## Known failure modes

- More than 100 measurements submitted — batch limit exceeded
- Non-integer millimetre values provided — integer-only constraint violated
- Invalid dataClass value outside 'public' or 'synthetic' enum
- Missing required fields in measurement objects
- Malformed input array — returns validation error
- Service unavailable or payment failure via x402 protocol

## How this service works

Classify up to 100 declared measurement intervals against tolerances as pass, fail or hold. Integer millimetres; uncertainty is an absolute interval half-width, not a confidence level. No sensor verification or engineering approval. New modular adapter: retained result recovery for 24 hours, minimal receipt metadata for 90 days. Existing live route unchanged.

## Output

Returns a classification result for each submitted measurement interval — each labelled as pass, fail, or hold — based on whether the declared measurement falls within, outside, or borderline against the specified tolerance. Results are retained for 24 hours; minimal receipt metadata is retained for 90 days.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "dataClass": {
   "enum": [
    "public",
    "synthetic"
   ],
   "type": "string"
  },
  "measurements": {
   "type": "array",
   "maxItems": 100,
   "minItems": 1
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/inspection-tolerance-batch-887d3fca/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)