Ask the sensor network a question.
An agent with direct read access to Mālama's live environmental oracle — hardware-signed readings, cross-validation against independent weather models, and the Merkle roots anchoring it all on Cardano. It answers from the record, not from training data.
Every answer traces back to a reading a machine signed.
The agent holds eight read-only tools over the live oracle. It cannot write, mint, or spend — it reads the same record anyone can verify on chain.
Ask anything about the fleet — or start with one of these.
Not a chatbot with a weather API. A network that signs its own data.
Every number the agent quotes has a device that measured it, a secure element that signed it, and a Merkle root that pins it to a public chain.
Sensors that sign inside the device
Orange Pi nodes with ATECC608B secure elements. The private key is burned in at manufacture and never leaves the silicon, so a changed digit breaks the signature.
Trust-weighted hex consensus
Readings are compared against neighbouring nodes and independent weather models inside each H3 cell. Disagreement is surfaced as a number, not smoothed away.
Daily Merkle anchors on Cardano
Each day's readings roll into a Merkle root anchored on mainnet, with a leaf per reading. Any single measurement can be proved against the published root.
ERCOT carbon intensity, hourly
Virtual nodes pull generation mix from EIA and derive grid carbon intensity, joined to the physical readings on time and place.
An audit trail of forecasts
Consumer weather models are scored against what the instruments actually measured, so the record shows which model was right and by how much.
Signature status on every answer
The agent can report which readings carried a verified hardware signature — including when the answer is "this one didn't."
Two questions free. After that, credits.
Queries run on our own GPU against live data. Credits never expire, and there is no subscription to cancel.
Your agent can read the network directly.
The same eight tools are exposed over MCP. Add one URL to an agent config — nothing to install. Machine callers settle per-request in USDC over x402; browsers use the credits above.
x402 · HTTP 402
Past the free allowance the endpoint answers 402 Payment Required with its price and pay-to address. Your agent pays in USDC on Base and retries with an X-PAYMENT header. No account, no key exchange, no invoice.