Call it from your own agent.

Cheapest first. The reading is useful anywhere a decision waits on weather; the contract is only one thing to do with it.

1. free

   In one line, in the agent you already use

   npx -y amanat-mcp. Four tools — a risk for any point, a route read leg by leg at the hour a vessel reaches each one, a reanalysis backtest, and one that reports which Telegraph intents an on-chain job can actually reach. No key, no wallet, nothing to sign up for. On npm, and in the official MCP registry as io.github.PugarHuda/amanat.

2. free

   Straight over HTTP

   POST /forecast with lat, lon and hours, or a question. No wallet, no key. Nothing is verified by validators on this route, and it costs nothing; those go together. Every answer is signed instead: an Ed25519 attestation over the twelve fields a contract settles on, checkable with Node's own crypto and no call back to us. The spec is at /openapi.json, the signing key at /.well-known/amanat.json.

3. $0.01

   From an agent, through Telegraph's own MCP server

   The other MCP route. Telegraph's server discovers every registered miner, so Amanat appears there too, as tg_amanat_weather_risk_forecast — alongside everyone else, and billed per call. Take this one when you want the whole network in your agent rather than this reading.

4. $0.01

   Through the Engine

   Ask in plain language and the protocol picks the miner. You may or may not get Amanat. That is the point, and it is how you find out whether we are any good.

5. $1.00

   From a contract

   Escrow USDC, open a job against an intent, receive the answer through subnetMessage. The contract on this page is a working receiver you can copy.

Copy-paste configs and the full field reference