Swap
Resolve a same-chain pair. For EVM swaps, quote the exact amount and wallet. Choose a route with partnerPreparation, then send its id to the prepare endpoint. For Solana, pass the quoted minimum into instruction preparation.
Agents are welcome here. Start without a key, find the exact asset or market, and show the wallet owner what they would sign.
curl -sS https://www.bitpont.com/api/v1/agentRead data.actions. Each entry gives the HTTP method, path and purpose. POST actions accept JSON. Successful results are in data. Save the response request ID when reporting an error.
curl -sS https://www.bitpont.com/api/v1/agent/tokens \
-H 'Content-Type: application/json' \
-d '{"chainId":"evm:1","q":"USDC","page":1,"limit":10}'Use the returned chain ID, exact token address and decimals. Tokens with the same symbol can be different assets. Follow data.nextPage until it is null.
Download the Bitpont MCP adapter and save it locally. In a client that supports stdio, choose node as the command and the absolute path to the downloaded file as its argument. Use Node.js 20 or newer. The adapter lists the agent actions, typed resource reads, portfolio planning, Treasury proposals and workflow tools. Each tool declares its inputs and access requirements. Keyless access is the default. For partner access set BITPONT_API_KEY in the local process environment.
{
"mcpServers": {
"bitpont": {
"command": "node",
"args": [
"/absolute/path/to/bitpont-agent-mcp.mjs"
]
}
}
}Read the product directory or search by task and product. Results give the REST path, MCP name and access scope. Follow nextPage to see every match.
curl -sS https://www.bitpont.com/api/v1/agent/tools \
-H 'Content-Type: application/json' \
-d '{"product":"treasury","q":"payment","limit":20}'Use the Treasury directory for the network and action. A scoped partner key can prepare a proposal. Keep its proposalToken and hash. Request the authorize stage for each owner who needs to approve. After the on-chain approvals meet the threshold, prepare and simulate the execute stage. Each transaction needs its own wallet signature. Reconcile the finalized receipt against the proposal hash. Token payments also require delivery checks.
Supply distinct recipients, atomic amounts and a run ID. Prepare one returned batch at a time. Check the exact transaction signature before continuing or retrying.
curl -sS https://www.bitpont.com/api/v1/agent/operations/workflow \
-H 'Content-Type: application/json' \
-d '{"network":"base","source":"aave","destination":"morpho","amount":"1.25"}'Open the returned review URL. For a custom sequence, use /api/v1/compositions/prepare. Check each step before funding the next one. GET /api/v1/agent/operations lists supported networks and operator-enabled execution services.
Resolve a same-chain pair. For EVM swaps, quote the exact amount and wallet. Choose a route with partnerPreparation, then send its id to the prepare endpoint. For Solana, pass the quoted minimum into instruction preparation.
Choose two different chain IDs. Request an indicative quote, or include both the source wallet and recipient for an executable quote. Review fees, minimum output, expiry and any warning before requesting the unsigned plan. Across and Circle CCTP support native USDC on Ethereum, Base and Arbitrum. THORChain supports native ETH to a mainnet Bitcoin payment address. These native routes carry their own fee terms.
Find opportunities by network and protocol. Read the exact vault, asset and wallet position. The Earn prepare endpoints cover supported deposits, withdrawals, lending actions, staking, claims and Pendle PT, YT and liquidity operations.
Read markets on Solana, Hyperliquid, GMX and Ostium. GMX and Ostium have unsigned order builders. Solana order preparation uses the native /api/tx/order endpoint with wallet authentication. Hyperliquid orders require the venue’s signed exchange flow.
Find listed underlying assets through the Options API. Open the returned workspace to review current strikes, premiums and expiries and authorize a Derive order.
Use the service directory for liquidity, Treasury, portfolio, orders and operations. The resource catalogue and integration manifest describe scoped account reads, batch requests and workflow drafts.
curl -sS https://www.bitpont.com/api/v1/agent/services \
-H 'Content-Type: application/json' \
-d '{"family":"perps","q":"order","limit":20}'Native endpoints keep their own wallet, session, rate and venue requirements. The action catalogue identifies the normalized API operations. A workspace link opens the product at its review screen.
curl -sS https://www.bitpont.com/api/v1/agent/earn/markets \
-H 'Content-Type: application/json' \
-d '{"network":"ethereum","limit":5}'curl -sS https://www.bitpont.com/api/v1/agent/perps/markets \
-H 'Content-Type: application/json' \
-d '{"venue":"ostium","cursor":"0"}'Read the Solana markets and use the returned market index. To prepare an order, POST its JSON body to /api/tx/order. The owner authorizes this individual API request by signing its exact path, timestamp and JSON body hash. Send the wallet public key in x-wallet, the Unix millisecond timestamp in x-ts and the base58 detached signature in x-sig.
velocity.api.v1|/api/tx/order|<timestamp-ms>|<lowercase SHA-256 hex of JSON.stringify(body)>Sign the UTF-8 bytes of that message. Use a fresh signature for each request. If the response requests account initialization, review that step first. Inspect and simulate the returned unsigned transaction before asking for transaction authorization. Open the Solana Perps workspace.
curl -sS https://www.bitpont.com/api/v1/agent/route \
-H 'Content-Type: application/json' \
-d '{"sourceChain":"evm:1","from":"0xa0b86991c6218b36c1d19d4a2e9eb0ce3606eb48","destinationChain":"evm:8453","to":"0x833589fcd6edb6e08f4c7c32d4f71b54bda02913"}'Open data.reviewUrl for the Bitpont ticket, or POST the same asset fields to /api/v1/agent/bridge/quote with an amount and slippageBps. For USDC with six decimals, "1000000" is one USDC. A slippage limit of 50 is 0.5%.
For a wallet-bound quote, also include sourceWallet and recipient. When executable is true, send the returned quoteId and the same addresses to /agent/bridge/prepare under the same API client. After the wallet submits, use the returned order identity and the source transaction hash with /agent/bridge/status.
All paths below are relative to /api/v1. The OpenAPI document specifies required fields and units.
POST /agent/treasury/safe/proposePOST /agent/treasury/safe/stagePOST /agent/treasury/safe/receiptPOST /agent/operations/asset/preparePOST /agent/operations/workflowGET /agent/productsPOST /agent/toolsGET /agent/operationsGET /agent/treasuryPOST /agent/treasury/solana/planPOST /agent/treasury/solana/preparePOST /agent/transactions/solana/statusPOST /agent/swap/cow/quotePOST /agent/swap/cow/approvalPOST /agent/swap/cow/cancel-intentPOST /agent/earn/aave/preparePOST /agent/earn/morpho-vault/preparePOST /agent/earn/morpho-blue/preparePOST /agent/earn/ethereum/preparePOST /agent/liquidity/concentrated/preparePOST /agent/liquidity/v4/preparePOST /agent/liquidity/receipts/preparePOST /agent/derivatives/boros/preparePOST /agent/perps/solana/order-intentPOST /agent/bridge/across/quotePOST /agent/bridge/across/preparePOST /agent/bridge/cctp/burnPOST /agent/bridge/cctp/mintPOST /agent/bridge/cctp/statusPOST /agent/bridge/thorchain/quotePOST /agent/bridge/thorchain/preparePOST /agent/operations/enso/quotePOST /agent/operations/enso/preparePOST /agent/earn/pendle/preparePOST /agent/optionsPOST /agent/earn/marketsPOST /agent/perps/marketsPOST /agent/perps/gmx/preparePOST /agent/servicesPOST /agent/swap/solana/quotePOST /agent/swap/solana/preparePOST /agent/earn/vault/preparePOST /agent/earn/etherfi/preparePOST /agent/earn/sparklend/preparePOST /agent/earn/fluid-credit/preparePOST /agent/earn/llamalend/preparePOST /agent/perps/ostium/prepareGET /agentGET /agent/networksPOST /agent/tokensPOST /agent/protocolsPOST /agent/routePOST /agent/swap/quotePOST /agent/swap/preparePOST /agent/bridge/quotePOST /agent/bridge/preparePOST /agent/bridge/statusCheck the network, wallet, recipient, spender, maximum input, minimum received, expiry and every fee. Protocol charges, gas, rent and Bitpont fees may be separate. Direct Earn and derivatives adapters retain the fee policy of their Bitpont workspace. See fees and execution.
Preparation produces unsigned instructions or a transaction. Rebuild the expected intent independently, simulate in the wallet, and request the owner’s approval for each signature. A token approval may require a later call to prepare the product action. For a bridge, check delivery after source confirmation. For an order, check fills or cancellation in its venue. Keep credentials, signatures and recovery phrases out of URLs and support messages.
The agent endpoints accept keyless requests when public access is enabled. Scoped partner keys use a server-side Bearer header. Private account reads and authenticated native actions retain their existing permissions. Use usage and the RateLimit response headers for the limits that apply to you.
On HTTP 429, wait for Retry-After. On an expired quote, request a fresh one and review the new terms. Partial data or a provider timeout is not confirmation of execution. Check the existing transaction or order before attempting another submission.
For a key or higher limits, email [email protected] with the operations you use and expected requests per minute.