bitpontBuild / API 1.9
Bitpont Protocol API | Credit, Vaults & Native Transfers
Discover Euler, Fluid, Spark, Yearn, Curve and Ostium resources. Understand account pagination, readiness, native-transfer recovery and adapter limits.
Public market discovery
Use connected-vaults.markets and connected-vaults.market with protocol, network and exact vault. Supported protocol identifiers are euler, fluid, spark and yearn. Euler supports Ethereum, Base and Arbitrum; the other vault catalogues are Ethereum. sparklend.markets, fluid-credit.markets, llamalend.markets, ostium.markets and ostium.market are also available within the public read budget.
Position coverage is paginated
With a positions:read key, use connected.positions for a selected wallet, network and protocol. Continue until nextCursor is null and retain failures. Euler reads only the explicit subaccount (0 by default). ether.fi withdrawal discovery scans bounded log ranges. Ostium scans one market and a bounded set of slots per page. A successful response never means complete net worth.
Detailed account resources also include connected-vaults.account, sparklend.account, fluid-credit.account, etherfi.account, etherfi.requests, etherfi.request, llamalend.account and ostium.account.
Execution remains in the owner review flow
These new v1 resources are read-only. They do not accept private keys or grant signing permission. The corresponding Bitpont product pages build and independently validate owner-signed actions. Enso route execution requires ENSO_API_KEY on the Bitpont server and is limited to same-chain ERC20 inputs and outputs. Its availability is distinct from the presence of a page.
Track native transfers accurately
Native USDC CCTP burns and destination mints are separate transactions. The Bitpont transfer page verifies the matching finalized mint. The scoped thorchain.progress resource follows a native ETH to BTC source hash; a confirmed Ethereum deposit is not delivery. Native BTC delivery needs the exact outbound payment and six canonical Bitcoin confirmations. Native ETH refund verification requires an RPC call trace.
Explicit integration limits
Across current API access is not integrated in this release. Bitcoin-funded THORChain swaps, Sanctum routed swaps and stake accounts, Fluid smart collateral/debt, arbitrary Yearn fee schedules, and CCTP destination hooks remain outside current coverage. None of these adapters silently extends universal cross-chain composition.