Trading integrations

On-chain spot, DEX swaps, and Hyperliquid perps. Discovery via MCP/CLI and execution via Execute Intent or wallet rails.

Provider families: trading, hyperliquid, fx, bridge, dogeos-*

Trading intents cover spot swaps (Kyber), perps, cross-chain funding, and chain-specific testnet venues. Thirdfy validates every action against the live catalog and your delegation scope before broadcast.

Venues

Credential model

Venue typeAuthority
On-chain EVM swaps (Kyber)User wallet, Gator/ERC-7710 delegation, or agent_wallet per runMode
Hyperliquid perpsOff-chain API wallet (venue signer), not ERC-7710. Bridge/funding txs may use Gator on EVM.
Bridge (Li.Fi)On-chain bridge txs via delegation or agent_wallet

See Delegation and protection for lane boundaries.

Discovery

  • MCP: getProviderActions with provider: "trading", hyperliquid, bridge, or fx
  • CLI: thirdfy-agent actions --provider <id> --json
  • REST: GET https://api.thirdfy.com/api/v1/agent/actions/catalog

Typical run modes

ModeWhen
thirdfy / hybridDelegated user capital with active Gator binding
agent_walletAgent-owned execution wallet (solo lane)
selfLocal signer; no delegation fan-out

Hosted deploy

Hyperliquid perps templates are available on EarnClaw (docs.earnclaw.com). EarnClaw hosts; Thirdfy governs execution.