Developers · Bots

Run deposit automation without inventing a rate manager.

A bot integration is not a browser flow with the buttons removed. It needs duplicate prevention, restart-safe state, explicit wallet custody, and a clear rule for when liquidity should be private.

Clone bot templatesRead Peerlytics guide
01

Bot sequence

  1. 01Load a Base wallet client from your own signer infrastructure.
  2. 02Call deposits(walletAddress) before creating a new deposit; reuse active inventory when it fits the order.
  3. 03Call offramp(walletClient, params) with integratorId and referralId so automation can be identified.
  4. 04Use otcTaker when the buyer is already known; otherwise the deposit is public fillable.
  5. 05Persist depositId, txHash, platform, currency, amount, and intended buyer context.
  6. 06Poll deposits(address) or Peerlytics deposit/intent reads so fills and closes survive process restarts.
02

Retry discipline

  • The SDK resumes undelegated deposits by delegating instead of creating a duplicate.
  • Browser idempotencyKey caching does not protect Node workers. Your worker should check deposits(address) before creating new liquidity.
  • If delegation fails after creation, retry the same wallet route; the resume path is designed for that state.
  • Do not retry USER_CANCELLED automatically. That indicates a signer rejected a prompt.
03

Useful bot patterns

Payroll or payout queue

Create one private OTC deposit per known buyer wallet, then send the returned link.

Treasury liquidity bot

Maintain a small delegated deposit on a preferred route and refill after reconciled fills.

Support reconciliation

Use depositId and txHash as the support handles, then reconcile with deposits(address).

Keep exploring

Offramp SDKDeveloper hub

Common questions

Can a backend create deposits without a user wallet?

Yes, if it has its own Base signer and USDC balance. The SDK signs through the viem WalletClient you provide; custody and key management are yours.

Does idempotencyKey prevent duplicate bot deposits?

No. idempotencyKey is browser-session backed. In Node or workers, use deposits(address) and your own order database to prevent duplicate inventory.