BUILD WITH BITPONT · API 1.2

Connect the data.
Carry the intent.

Bring supported market data, positions and financial actions into your application. Keep exact asset identities, explicit limits and a clear handoff to wallet approval.

A SMALL CLIENT. AN EXPLICIT CONTRACT.

Your first integration.

  1. Obtain a scoped API key from the deployment operator.
  2. Import the server-side client. Keep the key in your server environment.
  3. Read /api/v1/resources for configured adapters and parameter schemas.
  4. Show fresh state and the exact proposal before handing control to its owner.

The SDK has no package dependencies. The bundled client is not published to npm. This release does not offer self-service keys, billing or a public uptime SLA.

Server-side JavaScript
import { BitpontClient } from './bitpont-client.mjs';

const bitpont = new BitpontClient({
  apiKey: process.env.BITPONT_API_KEY
});

const markets = await bitpont.read(
  'hyperliquid.markets', { kind: 'perp' }
);

// Amount is a human-readable USDC string.
const review = await bitpont.prepareTreasury({
  chainId: 1,
  safe: SAFE_ADDRESS,
  owner: OWNER_ADDRESS,
  action: 'lending-supply',
  amount: '100'
});

// Display the proposal. The owner decides whether to approve.
console.log(review.data.proposal, review.data.reviewUrl);

DISCOVER THE EXACT SURFACE

Resources you can build on.

Each resource declares its scope and accepted parameters. Configured adapters can still have unavailable or partial upstream data.

treasury.account

positions:read

chainId * safe *

One bounded response · * required

treasury.lending

positions:read

chainId * safe *

One bounded response · * required

transactions.status

positions:read

network * hash *

One bounded response · * required

hyperliquid.markets

discovery:read

kind dex

One bounded response · * required

hyperliquid.book

discovery:read

kind dex market *

One bounded response · * required

hyperliquid.chart

discovery:read

kind dex market * interval

One bounded response · * required

hyperliquid.account

positions:read

wallet * user dex

One bounded response · * required

pendle.markets

discovery:read

network * cursor expired

Paginated · cursor reported in the response · * required

pendle.market

positions:read

network * market * wallet

One bounded response · * required

morpho.markets

discovery:read

network * cursor

Paginated · cursor reported in the response · * required

morpho.market

positions:read

network * marketId * wallet

One bounded response · * required

morpho.positions

positions:read

network * wallet * skip

Paginated · cursor reported in the response · * required

liquidity.position

positions:read

network * protocol wallet * tokenId *

One bounded response · * required

liquidity.positions

positions:read

network * protocol wallet * cursor

Paginated · cursor reported in the response · * required

solana-liquidity.pool

discovery:read

provider * address *

One bounded response · * required

solana-liquidity.position

positions:read

provider * pool * position * wallet *

One bounded response · * required

solana-liquidity.positions

positions:read

provider * pool * wallet * fresh

One bounded response · * required

boros.markets

discovery:read

cursor matured

Paginated · cursor reported in the response · * required

boros.market

discovery:read

marketId *

One bounded response · * required

boros.portfolio

positions:read

wallet *

One bounded response · * required

gmx.markets

discovery:read

No parameters

One bounded response · * required

gmx.account

positions:read

wallet *

One bounded response · * required

22 resources

FROM INTENT TO OWNER REVIEW

Prepare a supported financial operation.

The Treasury endpoint constructs an unsigned Safe proposal for USDC supply, withdrawal, variable-debt repayment or repayment using supplied USDC on Ethereum and Base.

It returns the exact contract calls, Safe nonce and hash, account checks, spending limit, simulation coverage and a Bitpont review link. Following the link makes no wallet request. The owner explicitly loads and reviews the proposal.

POST /api/v1/transactions/treasury/prepare
Required scope: transactions:prepare

Open Treasury →

RELIABILITY IS PART OF THE CONTRACT

Keep uncertainty visible.

  • Every response has a request ID. Retryable failures are explicit.
  • Read batches retain successful results and identify failed items.
  • Freshness and pagination travel with the data. Missing balances never become zero.
  • Transaction tracking distinguishes pending, included, reverted and not found.

A transaction included in a block is not proof of a protocol fill, finality, or destination delivery. Check the relevant protocol events before advancing a financial workflow.