Inspection Tolerances
by Inspection Tolerance Batch in Security & trust
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.
https://www.mahastrategies.com/api/v1/verify/inspection/tolerances- Price
- $0.01
- per call in USDC
- Uptime
- 100%
- last 30 days
- Response time
- 175 ms
- 175 ms slowest 5%
- Last check
- Passed
- 1 h ago, next any minute now
Reliability
How to call it
POST https://www.mahastrategies.com/api/v1/verify/inspection/tolerances
Each call costs $0.01001 in USDC on Base, paid with the request over x402.
Run a free test callOne unpaid request, the way an agent sends it. You see the payment challenge it gets back. Nothing is charged.
Example request
From the listing.
POST https://www.mahastrategies.com/api/v1/verify/inspection/tolerances
content-type: application/json
{
"dataClass": "synthetic",
"measurements": [
{
"id": "within",
"offsetMm": 3,
"toleranceMm": 5,
"uncertaintyHalfWidthMm": 2
},
{
"id": "overlap",
"offsetMm": 5,
"toleranceMm": 5,
"uncertaintyHalfWidthMm": 2
},
{
"id": "outside",
"offsetMm": -8,
"toleranceMm": 5,
"uncertaintyHalfWidthMm": 2
}
]
}Parameters
| Parameter | Type | Required | Description |
|---|---|---|---|
dataClass | string | Yes | One of: public, synthetic. |
measurements | array | Yes |
Example response
The provider's example. We can't check it without paying.
Example response, 44 lines
{
"data": {
"chargedAmount": "10010",
"inputHash": "sha256:a2969fabb5b74a743f89a1d014975bd68dc5a64238519cd5e4dde9deb…",
"limitations": [
"Public or synthetic inputs only. Caller labels are declarations,…"
],
"productId": "inspection-tolerance-check",
"result": {
"approvalGranted": false,
"basis": "synthetic",
"limitations": [
"Inclusive tolerance boundaries; overlapping uncertainty interval…"
],
"method": "inspection-tolerance-check/1",
"rows": [
{
"id": "within",
"metrics": [
{
"name": "lowerMm",
"value": "1"
}
],
"relatedIds": [],
"status": "pass"
}
],
"totals": [
{
"name": "passCount",
"value": "1"
}
]
},
"resultHash": "sha256:7381af8f881d2ae9aabeaabfb006202b3a07286e81c78dce57a08c928…",
"sourceContractAmount": "29000",
"version": "maha-legacy-adapter/1"
},
"proof": {
"settlement_id": "0x00000000000000000000000000000000000000000000000000000000000000…"
},
"success": true
}Call it from code
The curl command shows the payment challenge. The JavaScript and Python versions pay and call, and never pay more than $0.01001.
curl: see the payment challenge
# bash or zsh: see the payment challenge. Nothing is charged.
curl -sS -g -i -X POST 'https://www.mahastrategies.com/api/v1/verify/inspection/tolerances' \
-H 'content-type: application/json' \
--data-raw '{"dataClass":"synthetic","measurements":[{"id":"within","offsetMm":3,"toleranceMm":5,"uncertaintyHalfWidthMm":2},{"id":"overlap","offsetMm":5,"toleranceMm":5,"uncertaintyHalfWidthMm":2},{"id":"outside","offsetMm":-8,"toleranceMm":5,"uncertaintyHalfWidthMm":2}]}'
# x402 v2 sends the challenge base64-encoded in the PAYMENT-REQUIRED header (v1 sends it in the body).
# To read the header:
curl -sS -g -o /dev/null -D - -X POST 'https://www.mahastrategies.com/api/v1/verify/inspection/tolerances' \
-H 'content-type: application/json' \
--data-raw '{"dataClass":"synthetic","measurements":[{"id":"within","offsetMm":3,"toleranceMm":5,"uncertaintyHalfWidthMm":2},{"id":"overlap","offsetMm":5,"toleranceMm":5,"uncertaintyHalfWidthMm":2},{"id":"outside","offsetMm":-8,"toleranceMm":5,"uncertaintyHalfWidthMm":2}]}' \
| grep -i '^payment-required:' | cut -d' ' -f2 | tr -d '\r' | base64 --decodeJavaScript: pay and call
// npm i @x402/fetch @x402/evm viem
import { wrapFetchWithPayment, x402Client } from "@x402/fetch";
import { registerExactEvmScheme } from "@x402/evm/exact/client";
import { privateKeyToAccount } from "viem/accounts";
// Pays at most $0.01001 per call.
const client = new x402Client().setSpendControls({ maxAmountPerPayment: "$0.01001" });
registerExactEvmScheme(client, { signer: privateKeyToAccount(process.env.EVM_PRIVATE_KEY) });
const pay = wrapFetchWithPayment(fetch, client);
// Not sure it's safe to pay? ToolVet checks it first for $0.005. Pay for that from a separate
// client: this one is capped at $0.01001 per payment. GET https://toolvet.app/api/v1/check?url=https%3A%2F%2Fwww.mahastrategies.com%2Fapi%2Fv1%2Fverify%2Finspection%2Ftolerances&method=POST
const res = await pay("https://www.mahastrategies.com/api/v1/verify/inspection/tolerances", {
method: "POST",
headers: { "content-type": "application/json" },
body: JSON.stringify({
"dataClass": "synthetic",
"measurements": [
{
"id": "within",
"offsetMm": 3,
"toleranceMm": 5,
"uncertaintyHalfWidthMm": 2
},
{
"id": "overlap",
"offsetMm": 5,
"toleranceMm": 5,
"uncertaintyHalfWidthMm": 2
},
{
"id": "outside",
"offsetMm": -8,
"toleranceMm": 5,
"uncertaintyHalfWidthMm": 2
}
]
}),
});
console.log(res.status, await res.text());Python: pay and call
# pip install "x402[requests,evm]"
import os
from eth_account import Account
from x402 import x402ClientSync
from x402.http.clients import x402_requests
from x402.mechanisms.evm import EthAccountSigner
from x402.mechanisms.evm.exact.register import register_exact_evm_client
# Pays at most $0.01001 per call.
client = x402ClientSync().set_spend_controls({"max_amount_per_payment": "$0.01001"})
register_exact_evm_client(client, EthAccountSigner(Account.from_key(os.environ["EVM_PRIVATE_KEY"])))
with x402_requests(client) as session:
res = session.post(
"https://www.mahastrategies.com/api/v1/verify/inspection/tolerances",
json={
"dataClass": "synthetic",
"measurements": [
{
"id": "within",
"offsetMm": 3,
"toleranceMm": 5,
"uncertaintyHalfWidthMm": 2,
},
{
"id": "overlap",
"offsetMm": 5,
"toleranceMm": 5,
"uncertaintyHalfWidthMm": 2,
},
{
"id": "outside",
"offsetMm": -8,
"toleranceMm": 5,
"uncertaintyHalfWidthMm": 2,
},
],
},
)
print(res.status_code, res.text)Security scan
No findings
We scan names, descriptions and tool definitions for hidden instructions and other prompt-injection patterns.
Recent checks
| When | Result | HTTP | Time | Price |
|---|---|---|---|---|
| 1 h ago | Passed | 402 | 211 ms | $0.01 |
| 11 h ago | Passed | 402 | 175 ms | $0.01 |