> For the complete documentation index, see [llms.txt](https://archer-bot.gitbook.io/archer.bot/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://archer-bot.gitbook.io/archer.bot/intents/perps.md). # Perps > **Status: not live yet.** Perpetual futures are on Archer's near-term roadmap. This page outlines what we're building so the surface is documented as it ships. ## What Perps Will Look Like in Archer Perpetual futures (perps) let you take leveraged long or short positions on a token without holding the underlying asset. Today, using perps means picking a venue (Hyperliquid, Drift, Jupiter Perps, GMX, dYdX), funding the right wallet on the right chain, learning each venue's UI, managing margin manually, and watching liquidation prices yourself. In Archer, you'll just say what you want: * *"Open a 5x long on SOL with $200"* * *"Short ETH with 3x leverage, $500 collateral"* * *"What's my open position on BTC?"* * *"Close my SOL long"* * *"Set a stop loss at $140 on my SOL position"* Archer handles venue selection (best funding rate, deepest liquidity, lowest fees), routes collateral from your existing balance, opens the position, and surfaces liquidation/funding/PnL in a single dashboard view. ## What We're Building Toward * **Venue routing.** Same logic as bridges and swaps — best execution across multiple perps DEXs, picked automatically. * **Cross-margin awareness.** If you have collateral on Solana but the best venue is on an EVM chain, Archer plans the bridge as part of the open. * **Risk previews.** Every Confirm modal shows liquidation price, funding rate, max loss, and the venue chosen — same level of clarity as a swap quote. * **MCP tool surface.** `open_perp_position`, `close_perp_position`, `get_perp_positions`, `set_stop_loss` — agents will be able to programmatically manage perps the same way they handle swaps today. ## Why It's Not Live Yet Perps add complexity along three axes that the current architecture doesn't yet handle end-to-end: 1. **Stateful positions.** Swaps and bridges are one-shot — perps live until closed or liquidated. The agent needs to track and manage long-running state. 2. **Risk surface.** A bad swap costs you slippage; a bad perp can liquidate your collateral. The Confirm modal needs richer risk disclosures, and the agent needs to refuse trades that obviously over-lever an account. 3. **Venue heterogeneity.** Each perps DEX has its own collateral model, oracle, liquidation engine. Building a unified abstraction takes more than a single integration. We're working through these. Updates will land here as the surface ships. If you're a perps power-user with strong opinions on venue priority or UX, reach out at [archerprotocol.com/contact](https://archerprotocol.com/contact). --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://archer-bot.gitbook.io/archer.bot/intents/perps.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.