Agent trading
Connect an assistant to an approved account while keeping trading intent and custody under your control.
Give an agent a defined role
Owner-approved automation
Drag to pan, or use arrow keys when the diagram is focused. Use plus and minus to zoom, and zero to fit. On a touch screen, pinch to zoom.
An agent can help inspect markets, review an account, preview an order or carry out an authorized trading action. It connects through an owner-approved API key for one existing account, using the public API directly or our optional MCP tools.
Choose read access for research and monitoring. Add trade access only when the intended task requires it. Connecting a client does not create an account, complete its secure setup or authorize a trade.
Read access and trading access have different purposes
The approved key limits the account and operations available to the agent. The venue still checks account readiness, market rules and risk controls for each action.
| Access | What it enables |
|---|---|
| Read | Inspect permitted account state, orders, positions and history; preview an order without submitting it. |
| Trade | Submit and cancel permitted orders, including an authorized reduce-only order to close a position. |
| Owner session | Complete secure setup, deposit, withdraw, approve agents and manage delegated keys in the browser. |
Define the trading task and its limits
A trade-scoped key enables trading operations. Your authorization defines what the agent may do: a specific action or a strategy operating within agreed limits. Specify permitted markets, direction, size, price constraints and reduce-only or post-only rules where relevant. A preview estimates an order; it does not reserve funds or authorize trading beyond that task.
An approved strategy can place orders within its defined limits without a separate human approval for each order. After an action, the agent should report the returned state, preserve the original identity if an outcome is unknown, and confirm order and position changes through account updates. Closing and cancelling also require trading authority.
Keep control of credentials and custody
Approve access in your browser after checking the client, account, code and requested scopes. Keep your passkey and owner session credentials private. The agent receives its own scoped key through its client, not your signing identity.
Choose the shortest practical access period. You can revoke a key from your owner session; an agent cannot approve its own renewal or broaden its scope. Expiry or revocation must stop new trading attempts. Review outstanding orders and positions separately, because ending credential access is not an order-cancellation instruction.
Start with a read-only connection
Edel Markets is on Devnet, with Testnet and Mainnet coming soon. Use the environment supplied for your account and complete secure setup in the app. Request read access, approve the client in the browser, then confirm account readiness and inspect a market before enabling any trading action.
For a tool-based assistant, continue to MCP connections. For a custom integration, see owner-approved agents, API keys and scope and agent permissions.