78trust / 100

Robotics Telemetry Condition Coverage Map

by Robotics Telemetry - Condition c in Weather & location

x402 APIPassing, checked 1 h ago

Require one satisfied observation precondition per requested check in the exact coordinate/clock/calibration Supplied-record analysis, not independent certification. Full contract at the free describe URL.

POST
https://www.mahastrategies.com/api/v1/compute/robotics-telemetry/condition-coverage-map
Price
$0.035
per call in USDC
Uptime
100%
last 30 days
Response time
227 ms
490 ms slowest 5%
Last check
Passed
1 h ago, next any minute now

Run a free test callHow to call it

Reliability

All checks passedSome failedAll failedNot checked

Status and outage history · Atom feed · Watch with other listings

How to call it

POST https://www.mahastrategies.com/api/v1/compute/robotics-telemetry/condition-coverage-map

Each call costs $0.035222 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/compute/robotics-telemetry/condition-coverage-map
content-type: application/json

{
  "calibrationDigest": "sha256:aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa",
  "checks": [
    {
      "calibrationDigest": "sha256:aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa",
      "checkRef": "calibration-pinned",
      "clockRef": "clock1",
      "frameRef": "frame1",
      "id": "c1",
      "state": "satisfied"
    }
  ],
  "clockRef": "clock1",
  "dataClass": "synthetic",
  "frameRef": "frame1",
  "nonpersonalMetadata": true,
  "requiredChecks": [
    "calibration-pinned"
  ],
  "robotRef": "robot-synthetic1"
}

Parameters

ParameterTypeRequiredDescription
calibrationDigeststringYes
checksarrayYes
clockRefstringYes
dataClassstringYes One of: public, synthetic.
frameRefstringYes
nonpersonalMetadatabooleanYes
requiredChecksarrayYes
robotRefstringYes

Example response

The provider's example. We can't check it without paying.

Example response, 29 lines
{
  "data": {
    "chargedAmount": "35222",
    "inputHash": "sha256:8afd3911b9abd55f9d46f06172d3967f4f54be495ecb601f2523e2a4c…",
    "limitations": [
      "Public or synthetic nonpersonal metadata only; these are caller …"
    ],
    "productId": "robotics-telemetry-condition-coverage-map",
    "result": {
      "authoritativeSourcesConsulted": false,
      "domainValidationEstablished": false,
      "findings": [],
      "method": "robotics-telemetry-condition-coverage-map/1",
      "metrics": [
        {
          "key": "robotics-telemetry-uniquely-satisfied-conditions",
          "recordId": "robotics-telemetry",
          "value": "1"
        }
      ]
    },
    "resultHash": "sha256:0adc10269e770bb10f6f421c3054af0527549b22cde886c9356c4d479…",
    "version": "maha-typed-metadata-audit/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.035222.

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/compute/robotics-telemetry/condition-coverage-map' \
  -H 'content-type: application/json' \
  --data-raw '{"calibrationDigest":"sha256:aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa","checks":[{"calibrationDigest":"sha256:aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa","checkRef":"calibration-pinned","clockRef":"clock1","frameRef":"frame1","id":"c1","state":"satisfied"}],"clockRef":"clock1","dataClass":"synthetic","frameRef":"frame1","nonpersonalMetadata":true,"requiredChecks":["calibration-pinned"],"robotRef":"robot-synthetic1"}'

# 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/compute/robotics-telemetry/condition-coverage-map' \
  -H 'content-type: application/json' \
  --data-raw '{"calibrationDigest":"sha256:aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa","checks":[{"calibrationDigest":"sha256:aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa","checkRef":"calibration-pinned","clockRef":"clock1","frameRef":"frame1","id":"c1","state":"satisfied"}],"clockRef":"clock1","dataClass":"synthetic","frameRef":"frame1","nonpersonalMetadata":true,"requiredChecks":["calibration-pinned"],"robotRef":"robot-synthetic1"}' \
  | grep -i '^payment-required:' | cut -d' ' -f2 | tr -d '\r' | base64 --decode
JavaScript: 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.035222 per call.
const client = new x402Client().setSpendControls({ maxAmountPerPayment: "$0.035222" });
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.035222 per payment. GET https://toolvet.app/api/v1/check?url=https%3A%2F%2Fwww.mahastrategies.com%2Fapi%2Fv1%2Fcompute%2Frobotics-telemetry%2Fcondition-coverage-map&method=POST
const res = await pay("https://www.mahastrategies.com/api/v1/compute/robotics-telemetry/condition-coverage-map", {
  method: "POST",
  headers: { "content-type": "application/json" },
  body: JSON.stringify({
    "calibrationDigest": "sha256:aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa",
    "checks": [
      {
        "calibrationDigest": "sha256:aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa",
        "checkRef": "calibration-pinned",
        "clockRef": "clock1",
        "frameRef": "frame1",
        "id": "c1",
        "state": "satisfied"
      }
    ],
    "clockRef": "clock1",
    "dataClass": "synthetic",
    "frameRef": "frame1",
    "nonpersonalMetadata": true,
    "requiredChecks": [
      "calibration-pinned"
    ],
    "robotRef": "robot-synthetic1"
  }),
});
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.035222 per call.
client = x402ClientSync().set_spend_controls({"max_amount_per_payment": "$0.035222"})
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/compute/robotics-telemetry/condition-coverage-map",
        json={
            "calibrationDigest": "sha256:aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa",
            "checks": [
                {
                    "calibrationDigest": "sha256:aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa",
                    "checkRef": "calibration-pinned",
                    "clockRef": "clock1",
                    "frameRef": "frame1",
                    "id": "c1",
                    "state": "satisfied",
                },
            ],
            "clockRef": "clock1",
            "dataClass": "synthetic",
            "frameRef": "frame1",
            "nonpersonalMetadata": True,
            "requiredChecks": [
                "calibration-pinned",
            ],
            "robotRef": "robot-synthetic1",
        },
    )
    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

WhenResultHTTPTimePrice
1 h agoPassed402255 ms$0.035
6 h agoPassed402490 ms$0.035
10 h agoPassed402218 ms$0.035
15 h agoPassed402209 ms$0.035
24 h agoPassed402227 ms$0.035