Bebop exchange profile

Bebop provides a wallet-connected swap application and trading APIs. Its request-for-quote service obtains prices from professional market makers; its aggregation service asks solvers to construct routes through external liquidity. These are different ways of sourcing a trade, even when the customer sees one purchase and one receipt in the application.[2]

DefiLlama recorded US$1,520,204,473 of rolling 30-day aggregator volume at 20:11:22 UTC on 20 October 2026. This is routed turnover, which overlaps execution at underlying venues. It does not establish a registered-user or active-trader count.[3]

Partial-fill support lets an EVM integrator reduce the amount taken from a quote. It does not create a standing exchange order for the unfilled amount. The Solana transaction route does not support the same partialFillOffset parameter. Multi-token construction and reduced fills therefore need separate capability checks in an integration.[6]

The application’s fee article, updated 22 August 2026, states a 0.1% swap fee. Its API pricing is separate and can depend on the agreement attached to an authentication key. A hypothetical US$10,000 swap therefore carries US$10 at the stated application rate, before network charges or other changes in delivered value. This calculation is not an executable quote.[8]

For a BopAMM router illustration, suppose gross output is 2,000 token units and the chosen fee is 25 basis points. The fee is 5 units and net output is 1,995. The documented minimum-output check occurs after that deduction. The router does not apply its BopAMM fee to the RFQ fallback leg; that does not establish that every cost of the alternative route is zero.[13]

The application can set slippage tolerance automatically, and the user can change it. Tolerance expresses the adverse execution movement the instruction accepts; it is not a separate guaranteed exchange fee. A quoted rate can become unavailable between inspection and execution.[10]

The aggregation API accepts a specified slippage percentage and returns a minimum acceptable output. A route that cannot deliver that threshold reverts; output above the threshold accrues to the taker under the documented mechanism. The permitted API range extends to 50%, so the maximum accepted parameter should not be mistaken for a sensible default.[14]

Integration monetization is a business arrangement rather than a universal retail rebate. Bebop describes both a configured fee applying across an integration and fees selected per quote. The partner’s displayed price and agreement should therefore be read together; a generic API access page does not establish a customer’s individual commercial terms.[32]

Permit2 changes how transfer authority is expressed, but it does not eliminate authorization. The wallet’s allowance to Permit2 and a trade-specific permission are separate steps. Approval targets can differ between RFQ, router and aggregation paths. Revoking an API key is consequently different from reducing an on-chain token allowance.[15]

The public API documentation describes client-submitted EVM transactions and a Solana transaction that the client signs and broadcasts with its blockhash constraints. A marketing reference to gasless execution should not be assumed to cover every public integration. No bank deposit or fiat withdrawal procedure was established for Bebop itself in the inspected execution material.[17]

Bebop’s exchange workflow moves assets from the connected wallet through settlement contracts. It does not require a standing exchange cash balance. This reduces reliance on an internal withdrawal queue, but leaves token approvals, settlement code and the selected network within the asset-control chain. Atomic settlement describes transaction behaviour; it does not insure token value or guarantee that a usable quote will always exist.[18]

The current audit index includes a June 2026 Cyfrin router review alongside earlier work by Offside, Nethermind and other firms. It expressly warns that listed reports may describe historical code rather than the exact production version. A report date and reviewed contract version matter more than the number of audit logos. No user compensation policy or individual insurance ceiling was established from this index.[21]

The privacy policy identifies Bebop Trading Limited as the British Virgin Islands controller. It covers information supplied through interactions with the service and describes data rights and retention qualifications. An application privacy request and control of a public blockchain record are different matters; removing a local wallet connection does not reverse completed transfers.[20]

The linked terms require users to be at least 18 and exclude specified US connections, Canada, Singapore and the People’s Republic of China, alongside legal and sanctions restrictions. They permit information requests and prohibit circumventing access controls.[19]

Wallet connection is not a promise that every connected address will receive a quote. Bebop’s screening guidance says the API or a market maker may decline transactions for particular wallets. A declined quote can therefore reflect an access decision, independently of wallet funding or the quoted asset’s price.[31]

Production access is also different from an unauthenticated demonstration. The authentication guide describes restricted, widened demonstration quotes without a key, while production RFQ and aggregation integrations require their own credentials. A successful test request should not be treated as proof of production capacity or the final commercial spread.[29]

These routes do not establish a staffed emergency dealing desk able to trade on the user’s behalf. When the interface or wallet is unavailable, checking the transaction’s chain status helps distinguish an unsubmitted instruction from a completed swap before attempting another trade.[25]

For a contractual dispute, the terms specify a written Notice of Claim to [email protected], including the earlier ticket and requested remedy. They provide JAMS arbitration, London hearings with permitted remote participation, and BVI governing law. The document also contains a one-year claim deadline and a 30-day arbitration opt-out window.[19]

The Trade History API can retrieve a wallet’s trades, or an integration’s own activity with the appropriate key. Its paginated history and transaction lookups expose execution records, token values, network fees and trade classifications. Integration credentials restrict integration-wide queries; they do not turn another customer’s private account into an authorized reporting scope.[27]

The explorer guide explains how to inspect transaction hashes, timestamps, status and gas charges, and points to explorer-based export functions. Such a CSV is transaction evidence, not a complete tax calculation: transfers, acquisition costs and activity elsewhere still need reconciliation. A default screen or one history page should not be presumed to contain every relevant event.[28]

The official site warns that the regulatory protections available for regulated financial services may not apply. No current firm-specific financial permission or deposit-compensation membership was established in the inspected company materials. The presence of tokenized stocks or other asset categories in the interface does not itself establish a securities permission or rights against an underlying issuer.[1]

Bebop’s terms remain dated 9 June 2022 at the current official link. That is the document date, not a claim that the terms were newly issued in October 2026. Bebop Trading Limited is the named contractual operator.[19]

The router guide describes an integration migration, not an instruction for customers to send funds to a new custody account. Previously granted allowances should be reviewed separately: changing application routing does not automatically cancel every old approval. Developers must match approval and transaction fields from the same current flow.[22]

Operator

Bebop Trading Limited

Exchange model

Decentralised

Service scope

Wallet swaps, market-maker RFQ and aggregation APIs.

Client types

Retail clients; Institutional clients

Pricing publication

Public and quoted pricing

Pricing scope

Published application fee; API and partner charges depend on the route and agreement.

Funding scope

Crypto wallets on supported networks.

Custody and asset handling

Wallet-held assets with transaction and allowance authorization.

Client eligibility

18+; excluded jurisdictions and sanctions restrictions apply.

Support

Official chat, email and integration support.

Authorisation and registration scope

No current firm-specific financial permission established.

Exchange metadata checked 20 Oct 2026Source 2Source 7Source 8Source 15Source 1Source 19Source 18Source 32Source 4Source 23Source 20

The wallet guide lists MetaMask, Rabby, Zerion, Rainbow, Phantom and WalletConnect-compatible choices. Connection support does not mean identical prompts or signing capabilities on every device and chain. The relevant control is the wallet’s actual transaction or permission request, including the selected network and recipient contract.[24]

A bot or AI interface still needs a transaction-signing path. An external application’s control of a signing key determines its authority. The execution documentation does not establish a native retail AI mandate, copy-trading subscription or managed exits when external automation disconnects.[17]