Bitpont MCP
Adaptateur MCP local pour la découverte des marchés DeFi, la consultation des portefeuilles et la préparation de transactions non signées. Les propriétaires de portefeuilles vérifient et signent les actions prises en charge.
Documentation
AI agent guides by task
Choose a task for its API request, MCP example and steps. Trading guides cover wallet permissions and how to check the outcome.
Getting started 6 guides
- Connect an AI agent to Bitpont with MCP Connect a remote or local MCP client, load the tools for one product, and test the connection with a public request before adding a wallet.
- Execute a DeFi trade from an agent wallet Sign and send a swap, bridge, lending transaction, perpetual order or rates trade using local MCP. Follow a Derive options order or volatility RFQ to its venue result.
- Sign wallet actions and recover an agent order Keep one private workspace across restarts, authorize agent or customer funds, and recover a submitted trade when an HTTP response goes missing.
- Validate a multi-tool DeFi workflow before execution Check up to twelve proposed tool calls together, identify field errors and signing requirements, and decide which steps your agent can run.
- Approve and revoke a customer trading session Let a customer approve specific trading tickets, give an agent access to only those actions, and preserve a wallet-signed path to revoke unused tickets.
- Batch dependent DeFi reads through the API or MCP Resolve a token and reuse its address in an amount conversion. Validate the calls, run the batch and handle an ambiguous or missing result. Portfolio and planning 4 guides
- Check a trading wallet before signing and verify its receipt Check gas, allowance, minimum output and borrowing capacity, then follow a Bitpont execution across Portfolio, REST and MCP.
- Compare DeFi liquidity protocols and plan a position exit Find the right liquidity adapter, compare the pool identities and live exit terms, and match a withdrawal to its position NFT or LP receipt.
- Resume a swap, vault or bridge task from Portfolio or MCP Plan a swap and vault deposit, preserve a gas reserve and resume the unfinished step after a browser close, agent restart or partial bridge delivery.
- Rehearse a position exit with Portfolio, REST or MCP Check a wallet-specific exit from lending, liquidity, derivatives, swaps, a bridge or a Safe. Save the plan, review signer requirements and recover its settlement evidence. Swaps and bridges 4 guides
- Quote token swaps and manage limit orders with an AI agent Compare EVM and Solana swap routes, inspect minimum output and fee collection, then follow a wallet-signed swap or a resting limit order.
- Quote a cross-chain bridge and verify destination delivery Resolve a token on both chains, prepare a direct deBridge transfer and use the order ID to distinguish source confirmation from destination delivery.
- Verify the tokens and fees from an agent swap Read one Jupiter or KyberSwap receipt from Portfolio or MCP. Check the transaction, the amount that reached the wallet and the fee Bitpont received.
- Find a trading pair and build an exact swap or bridge quote request Resolve token symbols on both networks, convert a display amount to base units and take the resulting request to a live quote provider. Lending and liquidity 6 guides
- Find lending markets, vaults and staking actions for an agent Read Earn opportunities by network, confirm the underlying asset and exit conditions, and prepare a supported deposit, withdrawal or claim.
- Find a liquidity pool and manage its position Find Solana pools by mint pair, identify an EVM concentrated-liquidity pool, and track the position created by a liquidity operation.
- Borrow against collateral and repay a DeFi loan Select the lending market for your collateral and debt assets, check the wallet’s borrowing capacity, then reconcile repayment and collateral release.
- Open and unwind a Solana Multiply position Check Jupiter Lend vault eligibility, size collateral and debt for a leveraged entry, and review the minimum swap proceeds needed to unwind.
- Compare Earn opportunities after costs for a chosen holding period Match an opportunity to its underlying token, compare provider-reported yield components and model a 90-day return with entry and exit costs.
- Check how much USDC a wallet can withdraw from lending Inspect the wallet’s fixed Aave and Morpho USDC positions on Base and Ethereum, then check an exact withdrawal amount before preparing it. Derivatives 7 guides
- Trade perpetuals and inspect funding-rate markets Find Hyperliquid, Solana, GMX and Ostium markets, select the correct account and signing flow, and track orders, fills and funding exposure.
- Read the options chain and place Derive limit orders Find a Derive contract, fund its eligible subaccount with Ethereum USDC, and follow a signed option order through partial fills, cancellation or settlement.
- Trade GMX V2 perpetuals on Arbitrum with an agent Find a GMX market, review USDC collateral and keeper fees, prepare an increase or decrease, and match the order key to the wallet’s position.
- Open, manage and reconcile an Ostium trade Select an Ostium pair on Arbitrum, review leverage and USDC collateral, protect the position and verify settlement using the original request hash.
- Trade and settle Boros funding rates on Arbitrum Choose a Boros rate market by collateral and maturity, inspect cross or isolated margin, and track orders, settlement and staged withdrawals.
- Build Hyperliquid spot and perpetual orders for the right market Resolve an exact Hyperliquid instrument, inspect its order book, review the intended spot or perpetual order, and reconcile fills with account activity.
- Initialize a Solana perps account and recover an order Select a Solana perpetual market and subaccount, sign the native order intent, and handle a required initialization, an empty cancellation or a missing receipt. Operations and recovery 4 guides
- Plan Treasury payments and multi-step Operations Choose a Safe or Solana Treasury workflow, verify payment recipients, collect the right approvals and recover each payment or operation by its own receipt.
- Build an agent portfolio view across wallets and positions Plan EVM and Solana wallet reads, follow resource cursors, and preserve partial results without double-counting receipt tokens or collateral.
- Check an EVM execution ticket before the wallet signs Read the wallet’s native and ERC-20 balances, verify token allowances and simulate the exact prepared ticket before submitting a transaction.
- Recover unfinished financial tasks after an agent restart Find outstanding tasks in the original workspace, refresh an individual task and resume a remaining step without repeating a settled transfer. Fees and settlement 4 guides
- Verify trading fees and manage an agent’s API limits Check free API usage, prove a supported Bitpont fee was received, and recover quota access without replaying a trade or emailing for a standard key.
- Track referral earnings and request payouts through the API Prepare and sign a Solana referral invitation, read qualifying fee receipts by source and request a reviewed payout from an available token balance.
- Reconcile partner swap fees and settlement events Match monthly workspace activity to transaction IDs, read fee evidence and reconcile referral payouts against the signed member ledger.
- Investigate a missing fee or settlement receipt Look up a workspace receipt by transaction ID, trace its recorded evidence and close a month using verified fees grouped by network and token.
Try a request
Run a public example against Bitpont. Each example reads data or prepares a draft.
{
"network": "base",
"from": "USDC",
"to": "ETH",
"limit": 3
}
Tool explorer
Find a tool by name, input or product. Open a result for its REST path and MCP schema.
1155 tools in the directory.
Downloads
Clients and SDKs
- MCP server Local stdio adapter with offline tool discovery
- Starter kit Adapter, examples, schemas and checksums
- Practice server Exercise trades and failure recovery on localhost
- JavaScript SDK Server-side client and wallet workflows
- Options MCP Options orders with an owner-controlled signer
API walkthroughs and signing reference
Make your first request
curl -sS https://www.bitpont.com/api/v1/agent
Read 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.
Connect an MCP client
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"
]
}
}
}
Find the right API tool
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}'
- Swap and limit orders — CoW order and cancellation signatures are submitted to their native endpoint. Market swaps return wallet transactions.
- Bridge — The source transaction and destination delivery have separate confirmations.
- Earn and borrowing — Review token permissions, then request a fresh preparation for the economic action.
- Perpetuals and rates — Solana uses a wallet-signed native request. Hyperliquid orders use venue signing. GMX, Ostium and Boros rates use wallet transaction tickets. Submit with executionSubmit or the local walletExecute tool.
- Liquidity pools and positions — Use the exact pool identity, fee tier and token order. Solana pool transactions use the native liquidity API.
- Portfolio — Plan reads for selected wallets. Follow cursors and retain partially available positions.
- Treasury — Safe owners collect approvals for one exact hash before execution. Solana payment batches require a separate wallet signature.
- Operations — Choose a supported route or compose up to twelve steps. Wallet approvals and settlement are tracked per step.
- Options — Read live contracts for a listed underlying. Use the local Options MCP from the agent kit for authenticated account reads, single-leg orders and two-to-four-leg volatility RFQs with your own wallet. The web workspace also supports venue login and signing.
- Hyperliquid spot and perpetuals — Inspect the exact protocol market, review live depth, then open the unsigned draft in the trading terminal.
- Business integrations — Choose a partner integration, estimate peak request units and send the workload brief to [email protected].
- Search, markets and help — Use exact asset addresses and paginate results.
- Referral programme — Sign the exact referral intent with your Solana wallet to use invitations, receipts and payout requests.
Manage a Safe proposal
Use the Treasury directory for the network and action. A free workspace 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.
Plan SOL or SPL payments
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.
Move funds between products
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.
Choose a product
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.
Bridge
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.
Earn
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.
Perpetuals
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.
Options
Find listed underlying assets through the Options API. Open the returned workspace to review current strikes, premiums and expiries and authorize a Derive order.
Other services
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.
Find a native endpoint
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.
Browse Earn and perpetual markets
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"}'
Prepare a native Solana perpetual order
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.
Resolve a USDC bridge from Ethereum to Base
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.
API endpoints and input schemas
Search the tool explorer by product or input. The API reference lists the available routes. For one tool, request its exact HTTP method, MCP name, input schema and access requirements.
curl -sS https://www.bitpont.com/api/v1/agent/tools/describe \
-H 'Content-Type: application/json' \
-d '{"tool":"derivativeWorkflow"}'
Download the complete OpenAPI document
Review, sign and verify
Check 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. Check the prepared intent and simulate it in the wallet. An agent signs with its own funded wallet. For customer funds, use the exact actions the customer authorized in a trading session. 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.
Access, limits and retries
The agent endpoints accept keyless requests when public access is enabled. Use openWorkspace for keyless trading. High-volume 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 sustained high-volume integration, email [email protected] with the operations you use and expected requests per minute.