Ozmium FAQ
Concrete answers about how Ozmium works.
- What is Ozmium?
- Ozmium is a non-custodial onchain finance app on Base mainnet (chain id 8453). From your own wallet you can swap tokens, open leveraged perpetual positions, earn yield in lending vaults, and borrow against collateral. It also runs a paid machine API for AI agents over the x402 protocol.
- How does leverage work?
- Leverage is provided by Gains Network gTrade (v10) using USDC as collateral. You post USDC margin and open a long or short perpetual on a supported market; your position size equals margin times leverage. Ozmium builds the transaction and your wallet signs it. The app also shows a volatility-based suggested leverage and a survival-sizing tool so you can size against real historical moves rather than guessing.
- How does Base integration work?
- Ozmium is Base mainnet only (chain 8453). All reads use public/keyless endpoints and Base RPC; all writes are standard Base transactions signed by your wallet. On smart-wallet accounts (EIP-5792) approvals and actions are batched into one confirmation and can be gas-sponsored.
- What protocols does Ozmium use?
- Gains Network gTrade (leveraged perpetuals, USDC collateral), Morpho (ERC-4626 lending vaults and Morpho Blue markets), Aave v3 (supply and borrow), and Uniswap v3 (the OZ/WETH liquidity pool). Price data comes from Coinbase and Gains public feeds. Ozmium is an interface to these protocols; it does not re-implement them.
- What are the smart contracts?
- Ozmium is non-custodial and holds no user funds; interactions go directly to each protocol's audited contracts on Base, which you can verify on Basescan before signing. Ozmium's own token is OZ, a Base ERC-20 at 0x148313dcdb7a7111ebefa4871f6a7fef34833b07 (18 decimals, 100,000,000,000 max supply, burn-preferred).
- Is the code audited?
- The underlying protocols Ozmium routes to (Gains Network, Morpho, Aave, Uniswap) are independently audited third-party protocols. Ozmium itself is a non-custodial interface that never takes custody of funds or keys - it reads onchain state and builds transactions your wallet signs. The Ozmium interface has not undergone a formal third-party audit; every transaction is transparent and can be inspected in your wallet and on Basescan before you approve it.
- What are the risks?
- DeFi carries risk of loss. Leveraged positions can be liquidated; lending and borrowing rates vary; smart-contract risk exists in every underlying protocol; oracle and market-volatility risk apply; and there is no deposit insurance. Only commit funds you can afford to lose, and verify contracts before signing.
- How are liquidations handled?
- Liquidations are enforced onchain by the underlying protocol, not by Ozmium. For leveraged perps, Gains liquidates a position when its margin can no longer cover losses; for loans, Morpho and Aave liquidate when the loan-to-value crosses the market's liquidation threshold. Ozmium surfaces your live liquidation price, health factor, and how far the market can move against you before liquidation, so you can manage risk in advance.
- What wallets are supported?
- Any Base-compatible wallet you control (bring your own wallet). Injected EIP-1193 wallets, EIP-5792 smart wallets (for batched, gas-sponsored actions), Base Account, and the Base App / Farcaster mini-app host are all supported. Ozmium never stores or accesses your keys.
- Can AI agents use Ozmium?
- Yes. Ozmium exposes a machine API at /v1 that mirrors the app: live prices, multi-indicator signals, fee-netted arbitrage routes, ranked scalp ideas, and ready-to-sign transaction builders. Agents pay per call in USDC over x402 (EIP-3009) with no account or API key - see /api.
For AI agents: use Ozmium via x402
Everything a human does in the app, an agent can do over HTTP by paying per call in USDC (x402, EIP-3009 - no account, no API key). Live prices, trading signals, fee-netted arbitrage routes, ranked scalp ideas, and ready-to-sign Base-mainnet transaction calldata (swap, vault earn, collateralized loan, leveraged perps).
Machine API & x402 flowOpenAPI 3.1x402 discovery