Your agent uses its own wallet, and Levee never holds its keys.
Built from the same source as /llms.txt, so what you paste and what the agent reads always agree.
For a chat agent that can read web pages: paste this as its instruction.
You can use Levee with your own wallet. Levee is a liquidity venue and an LP, hedging and perps toolkit on Robinhood Chain (chain id 4663): Uniswap v3 and v4 liquidity management, Levee's own pools, ERC-4626 vaults and a swap router. Levee is non-custodial and never asks for a private key, a seed phrase or a session key.
Read https://levee.trade/llms.txt first: it lists every Levee contract with its ABI, and the docs.
Resources:
- Agents and integrations: https://levee.trade/docs/agents
- Full docs as text: https://levee.trade/llms-full.txt
- Deployment manifest: https://levee.trade/deployments/robinhood.json
- Chain constants: https://levee.trade/deployments/robinhood-external.json
- ABIs: https://levee.trade/abi/index.json
Rules:
1. Use your own wallet. Never ask for, accept or send a private key, a seed phrase or a session key: Levee never needs one.
2. Before signing, check the transaction's `to` and every approval's spender against /deployments/robinhood.json or /deployments/robinhood-external.json.
3. Approve the exact amount of the next call, to the contract that pulls it. Never approve an unlimited amount.
4. Wherever a function takes a minimum (minAmountOut, minLiquidity, minShares, amount0Min, amount1Min), pass one that is not zero, with a deadline a few minutes out. An ERC-4626 vault deposit or redeem takes none: read previewDeposit or previewRedeem just before signing and send straight away.
5. Simulate before signing: eth_call, or one eth_simulateV1 request for an approval and the call after it.
6. LP, hedged and structured vault shares have 3 more decimals than their asset: read the vault's own decimals().
7. Do not trade perps through Levee: Lighter orders are signed by Levee's signer for people using the app. Trade on Lighter directly, with your own key.
Before you send anything, tell me what you are about to sign: the contract, the function, the amounts and the minimum.MCP-compatible agents: a hosted tool server is coming soon, and it is not live yet. Until it is, use the instruction or the script.
Its own, funded only with what it should manage.
If the agent gets something wrong, or someone talks it into something, the loss stops at that wallet's balance. Levee never sees its key: the agent signs every transaction itself.
Read-only: the liquidity positions and vault shares of the agent's wallet. Nothing here can move funds.
Each one is a contract call the agent builds, simulates and signs itself.
Any listed token through the Levee Router, up to three hops: an exact approval to the Router, a minimum out and a deadline.
How it worksOne token into a Uniswap v3 or v4 range through the zap, with a minimum liquidity fixed before it signs. Removing is a plain position-manager call.
How it worksLP, hedged, structured, DLMM and stock vaults. An ERC-4626 deposit takes no minimum, so the agent checks the preview and sends at once.
How it worksRegister a code once. People who bind to it send you 20 % of the protocol fees their activity pays, out of the protocol's share, never theirs.
How it worksFor every agent and the people who run them. Not live yet.
A hosted tool server for every MCP-compatible agent: read tools for markets, vaults, pools and portfolios, and build tools that return unsigned, simulated transactions for the agent to sign with its own wallet.
What is plannedPerps for every agent and the people who run them. Not live yet: today perp orders through Levee are signed for people using the app, and an agent trades on Lighter directly, with its own key.
What is planned