Bebop enables applications to execute gasless or self-executed token swaps using a request-for-quote (RFQ) model that eliminates slippage. This guide demonstrates how to integrate Bebop’s swap functionality with Privy embedded wallets.Documentation Index
Fetch the complete documentation index at: https://docs.privy.io/llms.txt
Use this file to discover all available pages before exploring further.
Prerequisites
Before implementing swaps, contact Bebop to receive the following credentials:- Auth Key – Enables authenticated API calls with improved rate limits and pricing
- Source ID – Identifies the application as an integration partner for revenue tracking
Setup token approvals
Bebop requires token approvals before executing swaps. Applications can use either standard ERC20 approvals or Permit2.Standard ERC20 approvals
To use standard ERC20 approvals, specifyapproval_type=Standard when requesting a quote from Bebop’s API.
Before executing a swap, the application must grant the Bebop settlement contract (0xbbbbbBB520d69a9775E85b458C58c648259FAD5F) an allowance to spend the user’s tokens.
Applications can also use Permit2 for approvals. Consult Bebop’s documentation for implementation
details.

