Actions & preflight

thirdfy-agent actions catalog, agent allowlist, and governance preflight before writes.

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.

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.

Authentication
Email OTP first-run onboarding, AGENT_API_KEY bootstrap, owner session, and execution-only mode for thirdfy-agent.
Run & status
thirdfy-agent run and intent-status for execute-intent jobs; JSON fields for automation.