LeverUpDeveloper Documentation

Build trading bots, interfaces, and analytics on top of the LeverUp perpetuals protocol on Monad.

Onchain Integration

Call the protocol directly from your own wallet. Full control, you pay gas, nothing between you and the contracts.

Contract guide

Sign trade intents offchain and let the protocol relay and pay for them. No wallet popups, no gas, sub-second submission.

1CT guide

Prices, pairs, positions, trade history, portfolio analytics, and leaderboards over plain HTTP.

API reference

You are building	Use
A trading bot or strategy that holds its own key	Onchain, or 1CT self-signing if you want gas covered
A frontend or wallet that trades on behalf of users	1CT — users authorize once, then trade without popups
A copy-trading or managed-account service	1CT with a hosted agent — per-action permission bits
A dashboard, indexer, or analytics product	REST API and onchain read functions

Most integrations combine two of these: the REST API for market and account data, and one of the execution paths for placing trades.

Three things account for most first-day integration bugs:

Units. qty is not in USD and not in wei — it is the base asset amount at 10 decimals. Read Precision & Units first.
Oracle data. Every price-sensitive call needs a fresh oracle payload fetched from the LeverUp backend, plus a native-token fee. See Core Concepts.
lvToken. Every position carries both the token you deposit (tokenIn) and the protocol's settlement token (lvToken). Getting the pairing wrong reverts. See Core Concepts.