Signals and market data

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

Provider families: allora, nansen, cmc, openmarket, openmarket-metrics, gmgn, fomo (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.

Typed signals

Each data read can publish signals in the signal manifest (thirdfy-app.json). A signal says what it measures, its typed fields and units, how fresh it must be, what one read costs, and whether a strategy may use it for direction, as a filter, or as context only.

  • Typed values. Typed reads return a typed block with numbers and ISO dates, next to the raw payload. Display strings such as "+6.26%" become 6.26.
  • Parse issues. parseIssues lists every field that could not be read, so a value is never guessed.
  • Freshness. freshness { fetchedAt, ttlMs, cacheHit } says when Thirdfy fetched the data and whether it came from cache.
  • Provenance. Each app says whether its values may be shown to users and which attribution line to show.
AppSignals today
CoinMarketCap13: fear and greed, market funding, open interest, BTC liquidations, BTC dominance, macro events, market regime, derivatives crowding, perp contract bias, and four context reads
Nansen1: Hyperliquid perps positioning
Allora1: price forecast gap
OpenMarket5: Hyperliquid perps snapshot, BTC funding, per-coin funding and open interest, Polymarket top markets
GMGN, Fomo APINone yet. Reads are raw context.

Signal manifest spec

Every field of thirdfy-app.json, roles, typed reads, credits, redistribution, discovery, and a complete example.

Integrations

Allora

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

Nansen

Hyperliquid perp screener, TGM intel, profiler reads, and premium research agent. Read-only via Thirdfy API.

OpenMarket

Candles, open interest, funding, liquidations and order flow on 11 exchanges, plus indicators, volume profile and screens for chart reading. Read-only via Thirdfy API.

GMGN

Token, wallet, KOL and smart-money reads on Solana, Base, BSC, Ethereum and Robinhood Chain. Read-only via Thirdfy API.

Fomo API

Unofficial fomoapi.io handle intel and app alerts. Read-only via Thirdfy API. Not the Fomo consumer app.

CoinMarketCap

Quotes, global metrics, fear and greed, and composed briefs. Read-only via Thirdfy API.

Venue matrix

Full provider key list for CLI and MCP discovery.

Credential model

Allora, Nansen, CoinMarketCap, OpenMarket, and GMGN are hosted through Thirdfy. CLI and MCP use ordinary Thirdfy auth. No extra venue key.

LayerModel
Allora / Nansen / CMC / OpenMarket / GMGN readsThirdfy CLI or MCP session. Thirdfy credits pay the action.
Execution elsewhereTrading, earn, and prediction venues use their own setup pages. See category hubs.

Discovery

  • MCP: getProviderActions { provider: "allora" }, { provider: "nansen" }, { provider: "cmc" }, { provider: "openmarket" }, or { provider: "gmgn" }. ?toolsets=signals adds a read-only toolset of the typed signal reads.
  • CLI: thirdfy-agent actions --provider allora --json, --provider nansen, --provider cmc, --provider openmarket, or --provider gmgn. thirdfy-agent signals --json lists every signal.
  • REST: GET https://api.thirdfy.com/api/v1/agent/actions/catalog. The top-level apps[] and each action's signals[] carry the manifest.

See Signal manifest.

Typical use

  1. Fetch Allora forecast (get_allora_market_forecast or get_allora_price_inference), Nansen HL research (get_nansen_perp_screener or get_nansen_position_intelligence), CoinMarketCap quotes and briefs (get_cmc_quotes, get_cmc_daily_market_overview), or OpenMarket chart reads (get_openmarket_candles, get_openmarket_metrics_indicators).
  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 EarnOrg may attach Allora output as advisory signalEvidence when operator env enables it. Deploy detail lives on docs.earnorg.com.

Example: one agent decision

An agent deciding whether to open a BTC long on Hyperliquid reads three providers, then checks the venue. The values are from real reads on 2026-10-08.

StepReadValueWhat it tells the agent
1get_cmc_fear_greedtyped.index 58, NeutralSentiment is not stretched
2get_cmc_market_regimemixed_transition, stay_selectiveNo strong trend; size down
3get_openmarket_btc_fundingtyped.latestRate 0.0001Longs pay 0.01% per 8h; mild crowding
4get_allora_market_forecastBTC 8h predictedValueCompare with the current mid for a gap
5getVenueReadiness (venue hyperliquid)ready: false, HYPERLIQUID_DEPOSIT_REQUIREDThe agent cannot trade yet: fund first

Steps 1 to 4 are reads. Only step 5 looks at the venue, and nothing is traded until it says ready: true.

MCP
CLI
agentRun { action: "get_cmc_fear_greed" }
agentRun { action: "get_cmc_market_regime" }
agentRun { action: "get_openmarket_btc_funding" }
agentRun { action: "get_allora_market_forecast", params: {"assets":["BTC"],"horizon":"8h"} }
getVenueReadiness { venue: "hyperliquid", agentKey: "0x<your agent key>" }

Or give the whole decision to your agent:

Using Thirdfy, read CoinMarketCap fear and greed and market regime, OpenMarket BTC funding
and the Allora 8h BTC forecast. Tell me if conditions favor a small BTC long, then check
whether my Hyperliquid venue is ready. Do not place any order.

Related

CEX integrations
CEX-backed actions via credentialRef. API keys stored in Thirdfy only; MCP and CLI never hold raw keys.
Signal manifest
thirdfy-app.json v1. One open format that says what each data read returns, what it measures, how fresh it is, what it costs and how a strategy may use it.