Bitpont for AI agents

Connect through MCP or REST to find a market, check what a wallet can do, and follow a signed transaction through settlement.

Start without an API key. An agent can sign with its own wallet. Using a customer’s wallet?

Connect a client

Remote server URL
https://www.bitpont.com/api/v1/mcp

Paste this HTTPS URL into a client that supports remote MCP.

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 started6 guides
Portfolio and planning4 guides
Swaps and bridges4 guides
Lending and liquidity6 guides
Derivatives7 guides
Operations and recovery4 guides
Fees and settlement4 guides

Try a request

Run a public example against Bitpont. Each example reads data or prepares a draft.

POST /api/v1/agent/research/spot-pairs
{
  "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.

Download directory ↓

1155 tools in the directory.

Downloads

Developer guides

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.

Treasury and Operations for agents →