External agents
Run your own AI agent and use DXAP for market data, trade execution, and portfolio tracking. Connect through MCP or REST, with a paper account for simulated trading or a live Hyperliquid account.
External agents are in beta. If something fails or is confusing, report the steps and any errors in the DXAP Discord. Keep API keys out of reports and screenshots.
How it works
Section titled “How it works”Your harness is the software running your agent. It controls the model, strategy, memory, and schedule. DXAP provides research and trading tools, applies configured trading limits, and records orders, fills, activity, and performance.
External agents do not use DXAP-hosted chat or autonomous schedules. Your harness decides when to act. Portfolio tracking continues while it is offline, and accepted orders can still fill.
Paper trading is exclusive to external agents. It uses simulated funds and does not require live funding or Hyperliquid trading approvals. Live trading requires a funded account and its trading and fee approvals; see Connect an account.
Create and connect
Section titled “Create and connect”- Open New Agent → Use your own harness.
- Name your agent, choose paper or live trading, and complete account setup. The agent’s runtime and selected account are fixed after creation; create another agent to use a different account or switch between paper and live.
- In the agent’s Harness connection area, click Connect agent. Review the permissions, choose a key name and expiration, and sign the request to generate your API key.
- Save the key in your harness’s secret configuration and connect using the instructions shown on the page.
| Connection | Address |
|---|---|
| MCP | https://mcp.dxap.ai/mcp |
| External-agent REST API | https://api.dxap.ai/api/v1/account/external-agent |
Both use the same API key as a Bearer token. MCP clients discover the available tools after connecting. For REST request details, use the OpenAPI schema.
Start with a read-only check, for example:
Show my connected agent, whether it uses paper or live trading, its positions, open orders, and trading limits. Do not place any trades.
Available tools
Section titled “Available tools”| Task | MCP tools |
|---|---|
| Get portfolio, limits, recent actions, and optional market context together | get_trading_summary |
| Inspect account readiness, positions, limits, and performance | get_account_context, get_portfolio, get_trading_limits, get_account_performance |
| Research markets, prices, funding, and technical indicators | get_market_overview, market_get_snapshots, market_technical_analysis |
| Read news and curated X commentary | market_news_get_signals, market_news_get_article, twitter_get_summaries |
| Open, reduce, or close positions with market or limit orders | submit_perp_market_order, submit_perp_limit_order |
| Edit or cancel eligible orders | modify_perp_limit_order, cancel_perp_limit_order |
| Set or cancel position take-profit and stop-loss orders | set_perp_exit_orders, cancel_perp_exit_orders |
| Review requests, execution outcomes, and current order state | list_actions, get_action_receipt, get_order |
The external REST API also supports trading, portfolio, and action-history workflows. Use MCP for the news, X, and technical-analysis tools listed above.
Which API key do I need?
Section titled “Which API key do I need?”The key created by Connect agent covers external trading and market research. It includes MCP access, market data, account context, action history, trade submission, and order management. It is bound to that external agent and its selected account. No second research key is needed.
To also investigate or manage DXAP-hosted agents, create a separate account REST key under Settings → API keys, selecting the read or write permissions needed. Account keys and external-agent keys serve different workflows; their permissions cannot be combined into one key. Hosted trade approvals stay on the DXAP website.
Trading and connection controls
Section titled “Trading and connection controls”- Set limits in DXAP. Use the agent’s settings for supported trading limits, and give your harness clear instructions about what it may trade. Generating a key does not start an autonomous strategy.
- Check fills, not just submissions. An accepted order may still be resting or partially filled. After a timeout, retrieve the original action receipt before retrying. Reuse the same
client_action_idfor an identical retry to avoid duplicate submissions. - Review protection changes. Replacing position TP/SL replaces the complete set of DXAP-managed position exits, so include every target and stop you want to retain. Attached exits on a limit entry activate only after the entry fully fills. See Orders.
- Stopping the harness does not close positions. Disabling trading or revoking an API key also leaves accepted orders and existing positions in place. Cancel orders or close positions separately when intended.
Start with the DXAP skills
Section titled “Start with the DXAP skills”The DXAP skills provide setup instructions and workflows for external-agent trading, market research, and investigating or managing hosted agents. They are a work in progress and a starting point for your own harness. Installing a skill does not configure credentials or start trading.