Skip to main content
Owly connects trading accounts through wallet signatures and authorized trading keys. Fund ownership and trading-key custody are different: you control the owning wallet, while an authorized API Wallet can execute trades and incur losses.

​
Account and key roles

See Account Type for the three current setup paths. Creating a native Hyperliquid sub-account is not required for the API Wallet path.

​
What an authorization permits

An API Wallet can sign supported trading actions, including opening and closing positions. It does not replace the owning wallet’s external withdrawal signature. This does not imply that an agent has no protocol-internal fund permissions. Review the connected owner address, API Wallet address, expiration, Builder fee limit, and any contract transaction before signing. Deposits and swaps can require separate token approvals. A token approval limit is different from a quoted swap spend limit.
A leaked trading API key can enable malicious trading and losses. Non-custodial fund ownership does not protect against market losses, liquidation, malicious trading, or protocol failure.

​
Protect and revoke access

  • Never send a seed phrase, owning-wallet private key, or trading API key to the Assistant, support, or chat.
  • Use a trusted device for Trade authorization. Clearing browser storage may remove locally stored trading credentials and pending-operation recovery; it does not revoke a Hyperliquid authorization.
  • Stop the affected bot and inspect remaining positions and orders. To revoke an API Wallet, use the owning master wallet on Hyperliquid’s API page.
  • Update the corresponding Owly authorization before restarting. LeverAcc uses its dedicated execution-wallet update flow.
  • Removing an Owly fund manager removes management access; it does not automatically stop running bots or revoke protocol authorizations.
For funding entry points and owner signatures, read Asset Management. For delegation scope, read For Asset Owners.