API-key trading is the mechanism that lets a tool place orders on your account without ever taking possession of your money. Instead of depositing funds somewhere, you generate a key — a kind of scoped credential — and hand that key to the software. The software uses it to read your balance and submit trades, but the account stays yours. Understanding how this works helps you grant exactly the access a strategy needs and no more.
What an API key actually is
An API key is a credential your account issues so that an external tool can interact with it programmatically. Think of it as a special-purpose pass rather than a master key. When a trading tool holds your key, it can talk to your account through an interface, sending instructions like "open this position" or "cancel that order" on your behalf.
Crucially, the key is not a transfer of ownership. Your funds remain in your account the entire time. The tool is acting as an agent that can operate within limits you set, not as a custodian that holds a balance. This is what makes API-key trading compatible with staying non-custodial: access and custody are two separate things.
The key can also be revoked. Because your account issued it, your account can invalidate it. The moment you do, the tool loses its ability to act, and it never had the ability to move your money out in the first place if you scoped the key correctly.
How permissions and scope work
The safety of API-key trading lives almost entirely in scope. Most systems let you decide what a key is allowed to do — read data, place trades, and in some cases withdraw funds are separate permissions. A well-scoped trading key grants only what a strategy needs to function, which typically means reading balances and placing orders, while withdrawal permission stays off.
This separation is the whole point. A key that can trade but not withdraw lets a tool run your strategy while being structurally unable to send your assets anywhere. Even if that key were exposed, the damage it could do is bounded by the permissions you granted. Scoping tightly turns a potential disaster into a manageable inconvenience.
Because of this, the discipline of API-key trading is to grant the minimum. Before you create a key, decide what the tool genuinely requires, disable anything it does not, and treat every extra permission as a cost rather than a convenience.
API-key trading with Liquid Edge
Liquid Edge uses this model directly. It is non-custodial by design and never holds your funds — you connect through an API key or an on-chain connection, and you retain custody throughout. The key gives the platform operational access to run your strategy on your Hyperliquid-native account, without any deposit into a platform wallet and with no KYC step.
In practice that means your automation acts against your own balance. A strategy you build in the platform can open and manage positions, but each of those positions lives in the account you control. If you want to stop, you revoke the key and the connection goes dark while your assets stay put. The connection was always operational access, never ownership, so removing it costs you nothing but the automation.
This design is why API-key trading and custody can coexist. You get software that trades for you and a balance that never leaves your hands, held together by a credential you can issue, scope, and revoke on your own terms.
Putting it into practice
API-key trading works when you treat the key as a scoped, revocable credential rather than a blank check. Create it with only the permissions a strategy needs, keep withdrawal access off, and revoke it whenever you choose. Because Liquid Edge is non-custodial and Hyperliquid-native with no KYC, an API key lets you automate while retaining full custody of your funds. Build and connect your first strategy in Strategy Studio.
Past performance is not indicative of future results. This material is educational and not financial advice.
