Actions & preflight

Find the actions your agent can call, browse data signals, and check a write before you run it.

Find the actions your agent is allowed to call, then check a write with Thirdfy before you send it. These checks catch problems early, before any funds move.

Find actions

# Your agent's actions
thirdfy-agent actions --json

# One provider
thirdfy-agent actions --provider hyperliquid --json

# One chain
thirdfy-agent actions --chain-id 8453 --json

# Search, one page at a time
thirdfy-agent actions --search funding --limit 20 --offset 0 --json

With an agent API key, actions lists the actions your agent can call. The CLI finds the key in --agent-api-key, THIRDFY_AGENT_API_KEY, or the config that email login saved.

  • If the agent's policy has an allowlist, you see only those actions.
  • With no agent key, you see the public catalog.
  • run and preflight are checked against the same list.

Each action shows its requiredParams, a paramsSchema and its behavior (readOnly, destructive, recommendedTimeoutMs).

Action names work with hyphens or underscores. get-cmc-fear-greed and get_cmc_fear_greed are the same action.

Paging

By default, actions prints the whole list. Add any of these flags to get one page at a time:

FlagUse
--search <text>Only actions whose name, description or aliases contain the text
--limit <n>Page size. Concise: 50 by default, at most 100. Detailed: 10 by default, at most 25
--offset <n>Skip this many matching actions (default 0)
--view concise|detailedconcise (default) keeps the fields needed to pick an action; detailed returns full entries with paramsSchema

Each page includes pagination (total, matched, offset, limit, returned, hasMore) and a hint with the next --offset to use.

Find data signals

thirdfy-agent signals --json

This lists every data app (Allora, CoinMarketCap, Nansen, OpenMarket) and the signals it publishes, with their fields, units and freshness. See Signal manifest.

Preflight

Preflight runs Thirdfy's checks on a write without sending it. It checks the run mode, the execution wallet and the shape of your params.

thirdfy-agent preflight --action place_hyperliquid_perps_order --provider hyperliquid \
  --run-mode agent_wallet \
  --params '{"coin":"ETH","isBuy":true,"size":0.01,"limitPx":2000,"orderType":"limit"}' \
  --json

For venue actions (Hyperliquid, Polymarket, Lighter, Veranta), also check that the venue is ready:

thirdfy-agent venue readiness hyperliquid --json

Preview

To ask whether Thirdfy would sign a write from the agent's own wallet, use preview. Nothing is sent, signed or billed. It returns:

  • wouldSign, and any blockedReason
  • an order and risk preview
  • the exact run command to send it
thirdfy-agent preview --action place_hyperliquid_perps_order --provider hyperliquid \
  --params '{"coin":"ETH","isBuy":true,"size":0.01,"limitPx":2000,"orderType":"limit"}' \
  --estimated-amount-usd 20 --json

For the full write sequence, see Run & status.

Provider setup

Each provider has an integration page with its setup steps, actions and examples:

ProviderPage
Hyperliquid (Bridge2 funding, API wallet, builder fees)Hyperliquid
Veranta perps on BaseVeranta
PolymarketPolymarket
LighterLighter
basedbid launchpadbasedbid
Solana (Jupiter, staking, lending, liquidity)Solana
Allora, CoinMarketCap, Nansen, OpenMarket, GMGN, Fomo APISignals and market data

You can also check the HTTP Actions reference or the live catalog at GET https://api.thirdfy.com/api/v1/agent/actions/catalog.