Signals and market data

Read-only forecast and analytics providers for agent decisions. No on-chain execution from these actions alone.

Provider families: allora (more read-only providers will appear here as the catalog grows)

These integrations supply advisory data for agent reasoning. They do not submit swaps, orders, or vault writes by themselves. Pair forecasts with venue evidence and Thirdfy preflight before any execute-intent.

Integrations

Allora

Network price inference for BTC, ETH, and SOL at 5m and 8h horizons. Read-only via Thirdfy API.

Venue matrix

Full provider key list for CLI and MCP discovery.

Credential model

LayerModel
Allora readsThirdfy API operator config (ALLORA_API_KEY on API host). No user wallet or CEX key required.
Execution elsewhereTrading, earn, and prediction venues use their own credential models. See category hubs.

Agents call catalog actions through CLI or MCP. The API holds the Allora key; integrators do not pass Allora secrets in tool params.

Discovery

  • MCP: getProviderActions { provider: "allora" }
  • CLI: thirdfy-agent actions --provider allora --json
  • REST: GET https://api.thirdfy.com/api/v1/agent/actions/catalog

Typical use

  1. Fetch Allora forecast (get_allora_market_forecast or get_allora_price_inference).
  2. Compare to venue mids or your own reference price (referenceMid optional param).
  3. Author intent only when setup, delegation, and preflight pass on the execution provider (for example Hyperliquid).

Hosted Hyperliquid templates on EarnClaw may attach Allora output as advisory signalEvidence when operator env enables it. Deploy detail lives on docs.earnclaw.com.

Related

CEX integrations
CEX-backed actions via credentialRef. API keys stored in Thirdfy only; MCP and CLI never hold raw keys.
Integrations and venues
Thirdfy execution venues by category. Trading, Yield, Prediction, and CEX integrations with named operator pages.