Agents and scripts paint ladders through the same endpoints the app uses. Every call returns transactions for the owner to sign.
HTTP endpoints
| Endpoint | Returns |
|---|---|
GET /api/pools | every DLMM Pro pool, deepest first: tick, spacing, price, fee |
GET /api/pool/:address | one pool and its book per tick: liquidity, open orders, fills |
POST /api/ladder/prepare | the open_limit_order transactions for a ladder, 25 ticks each |
POST /api/ladder/delegate | turn auto-collect on or off for one order |
POST /api/ladder/cancel, /close | collect filled ticks, close an empty order |
POST /api/swap | an exact-in DLMM Pro swap with the platform as referral host |
GET /api/orders?owner= | the orders whose NFT a wallet holds |
GET /api/ledger | the keeper's records, folded |
curl -s https://dlmmfee.org/api/ladder/prepare -H 'content-type: application/json' -d '{
"pool": "<pool address>", "owner": "<your wallet>", "side": "ask",
"rungs": [{ "tick": -81920, "amount": "250000000" }, { "tick": -81792, "amount": "250000000" }]
}'MCP server
The site serves an MCP endpoint at /mcp (JSON-RPC over HTTP POST). Tools: list_pools, read_pool, paint_ladder (a range, a rung count and a budget, returns the signed-ready batch) and block_sale.
{ "jsonrpc": "2.0", "id": 1, "method": "tools/call",
"params": { "name": "paint_ladder", "arguments": {
"pool": "<pool>", "owner": "<wallet>", "side": "bid",
"fromTick": -86000, "toTick": -83200, "rungs": 20, "budgetRaw": "2000000000" } } }Signing
Responses carry base64 legacy transactions. Each order's NFT mint has already partial-signed; the owner signs the rest and sends them to any RPC (or to POST /api/send). Blockhashes expire after about a minute, so prepare right before signing. Questions go to the X account.