how it works
Three calls. Zero trust required.
Your robot speaks plain HTTPS and JSON. Hoodly handles the chain. The same two calls work for AI agents and other autonomous systems. Here is the whole pipeline, end to end.
claim
Announce the task before doing it
Register a robot in the dashboard and drop its API key into the stack — ROS node, PLC bridge or a five-line script. Before executing anything, the robot claims the task. That ordering matters: the claim exists before the work, so evidence can't be invented after the fact.
{
"title": "Inspect conveyor belt section B",
"expected_result": { "frames": 120, "route": "B1-B4" }
}
→ 201 created
{
"task": {
"id": "8f14e45f-…",
"status": "claimed"
}
}
prove
Submit the evidence, get a fingerprint
When the task finishes, the robot posts whatever proves the work: telemetry, sensor readings, results. Hoodly canonicalizes the JSON — keys sorted, whitespace stripped — and computes a keccak256 hash. Same evidence, same hash, every time. One flipped byte, completely different hash.
fingerprint
{ "frames": 120, "route": "B1-B4", "anomalies": 0 }
0x9c22ff5f21f0b81b113e63f7db6da94fedef11b2119b4088b89664fb9a3cb658
anchor
Carved into Robinhood Chain
The hash rides inside the calldata of a 0-ETH transaction — timestamped by the block, immutable forever, publicly visible in the explorer. No smart contract sits in between: there is no deployed code, no upgrade keys, no audit surface. The chain itself is the notary.
then anyone checks
Verification is re-hashing.
Take the original evidence, hash it again, compare against the calldata on-chain. Match — the claim held. Mismatch — someone touched the data. Auditors, customers and insurers can do this without a Hoodly account, via the public endpoint or straight in the block explorer.
{
"verified": true,
"task": {
"title": "Inspect conveyor belt section B",
"robot": "warehouse-arm-01"
},
"anchor": {
"tx_hash": "0x4a8b17e2…",
"block_number": "1284930",
"explorer_url": "https://robinhoodchain
.blockscout.com/tx/0x4a8b…"
}
}beyond robots
Built for fleets. Open to agents.
Hoodly is designed around robot fleets — ROS nodes, AMRs, arms, humanoids. The primitive underneath is deliberately thin: claim a task, submit JSON evidence, get an on-chain receipt. An AI agent that logs tool calls and outcomes uses the exact same API. No second product, no special mode — if it can speak HTTPS, it can anchor.
the fine print, upfront