iotwerk_sensor_calibration

iot.halowerk.com · 10 paid endpoints · listed 2026-10-27

Canonicalizes device_id, nonce and message, computes an HMAC-SHA256 tag with caller-supplied ephemeral key material, and optionally compares a claimed tag in constant time. It does not provision devices, store keys or replace asymmetric device identity; do not submit long-lived production secrets.

livelast check 5 days ago
100%valid x402 answers, 72 h
sharedUSDC received on Base, 7 days
25distinct payers, 7 days
65.7score (0-100)

Paid endpoints

MethodEndpointPriceNetworks
POSTiot.halowerk.com/v1/device-auth
Canonicalizes device_id, nonce and message, computes an HMAC-SHA256 tag with caller-supplied ephemeral key material, and optionally compares a claimed tag in co
$0.002Base
POSTiot.halowerk.com/v1/battery-degradation
Applies a transparent heuristic: cycle fade scales with equivalent full cycles and depth-of-discharge exponent; calendar fade scales with square-root time and a
$0.003Base
POSTiot.halowerk.com/v1/fleet-anomaly
Computes cohort median, median absolute deviation and robust z-scores for one numeric reading per device. A caller-selected threshold determines flags. It detec
$0.003Base
POSTiot.halowerk.com/v1/lora-coverage
Computes free-space loss at one metre, applies a caller-supplied path-loss exponent over distance, then reports estimated receive power and margin against recei
$0.003Base
POSTiot.halowerk.com/v1/ota-sign
Canonicalizes firmware hash, version, device model and minimum bootloader version, then produces a SHA-256 manifest digest and HMAC-SHA256 release tag using cal
$0.003Base
POSTiot.halowerk.com/v1/sensor-calibration
Fits reference = slope × observed + offset with ordinary least squares over paired caller-supplied readings. It reports residual diagnostics and does not claim
$0.003Base
POSTiot.halowerk.com/v1/digital-twin-sync
Groups caller-supplied scalar field changes by field name, selects the highest version, and reports a conflict when equal-version values differ. It does not con
$0.004Base
POSTiot.halowerk.com/v1/edge-compute-bid
Filters caller-supplied bids by CPU, memory and latency constraints, computes workload cost from quoted unit prices, and ranks feasible candidates by total cost
$0.004Base
POSTiot.halowerk.com/v1/mesh-route
Computes a deterministic shortest path over caller-supplied directed or bidirectional links with non-negative costs. It does not measure live radio conditions,
$0.004Base
POSTiot.halowerk.com/v1/robotic-path-clearance
Computes the minimum Euclidean distance from each circular obstacle center to every path segment, then subtracts obstacle radius and robot radius. It detects pl
$0.004Base

Latest checks

WhenEndpointHTTPmsResult
5 days agoiot.halowerk.com/v1/battery-degradation402231valid x402 v2 terms

Income on Base (7 days)

This provider's payout address is shared by several providers, so its income is not shown as its own.

Is this your API?

Add the live badge to your docs:
<a href="https://logicnodes.io/observatory/p/iot.halowerk.com"><img src="https://logicnodes.io/observatory/badge/iot.halowerk.com.svg" alt="x402 status"></a>
x402 status badge
Claim it for free with x402_provider_claim (sign with your payout address), and get an alert within minutes when it stops answering with x402_monitor_create ($5 for 30 days). Both work over MCP (https://logicnodes.io/mcp/v2) or POST https://logicnodes.io/v1/tools/<tool>.

Income is all USDC received by the provider's payout address on Base, whatever the source. Score: 0-100: 50 x share of checks in the last 72 h that returned valid x402 payment terms + 30 x min(1, log10(1 + USDC received in 7 days) / 4) + 20 x min(1, log10(1 + distinct payers in 7 days) / 3). A provider never checked scores on income only; income is all USDC received by its payout address on Base, whatever the source. JSON: /v1/observatory/providers/iot.halowerk.com