Bebop

Bebop supports trading several tokens in one transaction. Its RFQ+ route requests quotes directly from market makers, while the Aggregator API draws on solvers and covers a broader token range. The separate Price and Trade History APIs help an application estimate a trade and record its result.

For a production integration, request an API key through Bebop's support page. The team supplies the key directly. Unauthenticated trading requests run in demo mode with wider quotes and heavy rate limits; the price stream requires authentication. Keep the key on your server rather than embedding it in a browser application. Public trade-history lookups are limited to a wallet address without a key.

The RFQ quickstart begins by retrieving supported chains and tokens. Use token contract addresses and decimal precision from that response, then request either a fixed selling amount or a fixed buying amount. The paying wallet and receiving wallet can differ. A quote provides an expiry time, an approval target and a transaction to sign. Read the approval target from each response because the required contract can change between quotes. Confirm the token approval before submitting the trade, and broadcast before the quote expires. Regular quotes typically last 60 to 75 seconds, depending on the chain.

Streaming prices serve a different purpose: they are indicative estimates for comparison before requesting an executable quote. The Price API sends snapshots over a persistent WebSocket connection, which the application must decode. It is useful for comparing available buying and selling prices without consuming a firm quote for every update.

Bebop advertises free API plans, but trading fees depend on the plan assigned to the key. Its browser app charges 0.1% on swaps, and network costs are separate. Confirm the key's commercial terms and throughput limit when arranging access. Bebop or its market makers may decline to quote for a wallet, so an integration needs to handle unavailable quotes as well as successful ones.