AgentFX — MCP gateway for Hyperliquid perps

AgentFX is a non-custodial Model Context Protocol server that lets autonomous AI agents place real perp orders on Hyperliquid. The agent owns its own EVM key — AgentFX only signs orders via an on-chain approveAgent grant. Flat 1 bps taker fee is captured on-chain via Hyperliquid Builder Code.

MCP endpoints

• Server (JSON-RPC 2.0, streamable-http): https://jdufibzebfwymvnyunti.functions.supabase.co/agentfx-mcp
• Manifest: https://solfun.dev/.well-known/agentfx-mcp.json
• OpenAPI: https://jdufibzebfwymvnyunti.functions.supabase.co/fx-api/v1/openapi.json
• Docs: /fx/docs

Tools exposed

• agentfx_enroll_config — on-chain addresses for approveAgent + approveBuilderFee
• agentfx_list_instruments — tradable Hyperliquid perp symbols
• agentfx_quotes — snapshot bid/ask
• agentfx_balance — live Hyperliquid accountValue + withdrawable USDC
• agentfx_enroll_status — re-verify on-chain approvals
• agentfx_place_order — place perp order (supports dry_run, client_oid)
• agentfx_list_orders, agentfx_cancel_order, agentfx_positions

How it works (for AI agents)

1. Agent generates its own EVM key and funds it with USDC on Hyperliquid.
2. Agent runs approveAgent + approveBuilderFee on-chain (one-time).
3. Agent mints an AgentFX API key and enrolls its wallet.
4. Every MCP agentfx_place_order call is signed by AgentFX as the approved agent and routed to the agent's own Hyperliquid account. The 1 bps fee is captured on-chain by the builder.
5. AgentFX cannot withdraw, cannot move USDC, cannot exceed the on-chain agent grant.

Honest disclosure

Perp trading carries real risk. Liquidations are real. AgentFX is a thin, non-custodial execution gateway — it does not custody funds, does not give trading advice, does not guarantee fills or latency.