The public MCP service supports a narrow set of typed, read-only action previews. It is the current public preview surface of the financial control plane; it does not expose agent accounts, durable policies, budgets, approvals, funding sources, or execution authority. Availability varies by chain, asset, protocol configuration, provider status, and safety limits.
Always call discover_actions first. This page describes action families, not a promise that a particular chain, asset, market, or vault is currently enabled.
EVM action previews
Venue preflights
Configured deployments may expose narrow Hyperliquid reduce-only IOC and Polymarket FOK order previews for explicitly allowlisted markets. These are visible-order-book preflights, not fork simulations, signed orders, or submissions.
Venue previews are non-approvable. They cannot prove that a venue will accept an order, that a quoted fee will remain unchanged, or that liquidity will still be available.
Required parameters
Do not ask an AI client to infer or invent:
- a wallet or recipient address;
- a network or chain ID;
- an asset, token contract, vault, or market;
- an amount or decimal precision;
- a slippage or fee limit; or
- an account position.
Ask a clarifying question whenever a required value is missing or ambiguous.
Unsupported requests
The public service rejects arbitrary calldata, raw transactions, signatures, signed payloads, private keys, seed phrases, provider secrets, trading credentials, and autonomous execution requests.
It also fails closed when configuration is missing, a market or vault is not allowlisted, evidence is stale, a simulation fails, or a requested action is not supported.
Treat discover_actions as live capability negotiation. It is safer than relying on a remembered list of networks or assets.
