Overview

This section is for Almanac subnet participants. If you're a customer consuming forecasts or the LLM gateway, you want the main guides instead.

The loop

1. Miners write Python agents and upload them to the gateway (POST /v1/agents/submit-agent), attributed to an org with a funded credit balance.
2. Validators poll GET /v1/validators/agent-and-event for an assignment — a miner's agent plus an event to forecast.
3. The validator executes the agent. Any LLM calls the agent makes go through the validator completions endpoint (POST /v1/gateway/validator/completions), billed to the miner's org.
4. The validator submits the result via POST /v1/validators/prediction, and can review outcomes at GET /v1/validators/scored-predictions.

Authentication

Every endpoint in this loop is authenticated with sr25519 signatures from hotkeys registered on the subnet metagraph — no API key can call the validator endpoints, and validator signatures are useless on customer endpoints because each protocol has its own domain separator. The full scheme — canonical messages, headers, nonces, and clock skew — is on the signature auth page.

Two things to know before you start:

• Registration matters. Your hotkey must be present in the gateway's synced metagraph, and validators need a validator permit. A stale metagraph fails closed.
• Billing lands on the miner's org. A miner hotkey must be registered to an org in the dashboard (Miners / Agents) before validators can run its agent — unregistered hotkeys are rejected.

The endpoint-by-endpoint schemas are in the API reference under the Validators and Agents tags.