Actions & preflight

Discover what the backend will accept:

thirdfy-agent actions --json
thirdfy-agent actions --agent-api-key "$AGENT_API_KEY" --json

Preflight validates policy, delegation, and parameter shape before queueing work:

thirdfy-agent preflight --agent-api-key "$AGENT_API_KEY" --action swap --json

Cross-check responses with the HTTP Actions reference and live GET https://api.thirdfy.com/api/v1/agent/actions/catalog.

Full flag matrix: full CLI reference (search “actions” / “preflight”).

Hyperliquid setup and builder fees

Hyperliquid perps use Bridge2 funding on Arbitrum and an API wallet approval before live orders. Start with provider discovery:

thirdfy-agent actions --provider hyperliquid --json
thirdfy-agent preflight --action get_hyperliquid_setup_status --params '{"mainWalletAddress":"0x..."}' --json

For runtime-owned funding and setup writes, prefer complete_hyperliquid_onboarding. Operator previews can still use get_hyperliquid_onboarding_plan and prepare_hyperliquid_onboarding.

Builder monetization parity: Thirdfy only enforces approve_hyperliquid_builder_fee when builder monetization is active (operator configured a builder address and the builder treasury has Hyperliquid margin). When the treasury is unfunded:

• get_hyperliquid_setup_status can return ready: true with warning HYPERLIQUID_BUILDER_WALLET_UNFUNDED
• get_hyperliquid_builder_fee_status returns monetizationEnabled: false with reason: BUILDER_WALLET_UNFUNDED
• place_hyperliquid_perps_order does not require builder approval

When monetization is active, get_hyperliquid_onboarding_plan includes approve_hyperliquid_builder_fee and setup status shows builder.enabled: true. A failed order with HYPERLIQUID_BUILDER_APPROVAL_REQUIRED means the main wallet still needs that approval while monetization is active.

Re-run get_hyperliquid_setup_status after funding, API wallet approval, and any builder step before placing perps orders.

Veranta setup (Base perps, formerly Avantis)

Veranta perps use Base USDC in the managed execution wallet. Thirdfy mints the stored delegate during onboarding. The catalog lists Veranta names (get_veranta_setup_status); the *_avantis_* names still work. Start with provider discovery:

thirdfy-agent actions --provider avantis --json
thirdfy-agent run --action get_veranta_setup_status --provider avantis --run-mode agent_wallet --chain-id 8453 --json

For runtime-owned setup, prefer complete_veranta_onboarding on chain 8453 with agent_wallet. It approves the wallet balance; pass targetCollateralUsdc for more. Operator previews can use get_veranta_onboarding_plan and prepare_veranta_onboarding. place_veranta_perps_order uses side long or short and takes takeProfitPrice / stopLossPrice at open.

Re-run get_veranta_setup_status after funding and onboarding before live orders. approve_veranta_builder_fee stays refused until Thirdfy's builder code is registered with Veranta.

See Veranta integration.

Allora forecasts (read-only)

Allora actions are advisory reads under provider allora. They do not replace preflight on execution providers.

thirdfy-agent actions --provider allora --json
thirdfy-agent run --action get_allora_market_forecast --params '{"assets":["BTC","ETH","SOL"],"horizon":"8h"}' --provider allora --json

See Allora integration and Market data.

Nansen research (read-only)

Nansen actions are advisory reads under provider nansen. They do not replace preflight on Hyperliquid or other execution providers.

thirdfy-agent actions --provider nansen --json
thirdfy-agent run --action get_nansen_perp_screener --params '{"date":{"from":"2026-08-27T00:00:00.000Z","to":"2026-08-28T00:00:00.000Z"},"pagination":{"page":1,"per_page":5}}' --provider nansen --json

See Nansen integration and Market data.

Fomo API (read-only)

Fomo API actions are advisory reads under provider fomo. This is an unofficial fomoapi.io integration, not the Fomo consumer app. Params use string chain slugs, not EVM chainId. These actions do not place trades.

thirdfy-agent actions --provider fomo --json
thirdfy-agent run --action get_fomo_search --params '{"q":"gkisokay","limit":5}' --provider fomo --json

See Fomo API and Market data.

basedbid (launchpad)

basedbid actions are under provider basedbid. Token list is a read on Base, Ethereum, and Robinhood Chain. LBP and flash create, buy, and sell are live writes on those three chains. Buy spends native ETH on the target chain. Confirm before any create or trade.

thirdfy-agent actions --provider basedbid --json
thirdfy-agent run --action basedbid_get_tokens --params '{"chainId":8453}' --provider basedbid --json
thirdfy-agent run --action basedbid_get_tokens --params '{"chainId":1}' --provider basedbid --json
thirdfy-agent run --action basedbid_get_tokens --params '{"chainId":4663}' --provider basedbid --json
thirdfy-agent run --action basedbid_create_flash --params '{"name":"Example","symbol":"EX","chainId":1}' --provider basedbid --run-mode agent_wallet --json
thirdfy-agent run --action basedbid_create_lbp --params '{"name":"Example","symbol":"EX","chainId":4663}' --provider basedbid --run-mode agent_wallet --json
thirdfy-agent run --action basedbid_buy --params '{"tokenAddress":"0x0000000000000000000000000000000000000001","amountEth":0.0001,"chainId":4663}' --provider basedbid --run-mode agent_wallet --json

See basedbid integration and Trading.