Builder API Key

The Builder API key identifies your application (layer 1). It is separate from the user JWT (layer 2) you get from EOA or weblink login. Catalog reads skip the builder key; login / register / weblink and user actions require it. Pass both when calling authenticated routes:

import { createBentoSdk, walletAuthProvider } from '@bento.fun/sdk';

const sdk = createBentoSdk({
  baseUrl: 'https://internal-server.bento.fun',
  apiKey: process.env.BENTO_BUILDER_API_KEY!, // required: x-builder-api-key
  auth: walletAuthProvider(() => ({ Authorization: `Bearer ${userJwt}` })),
});

Generate a key (testnet)

Use the form below during hackathons. Keys are minted only on the testnet markets host (internal-server.bento.fun). This site never creates mainnet keys.

Copy the key immediately. It is shown once. Store it as BENTO_BUILDER_API_KEY (or NEXT_PUBLIC_BUILDER_API_KEY for browser apps) and pass it as apiKey to createBentoSdk.

How it fits with auth

See Authentication for EOA and weblink user login.

Mainnet

Production / mainnet Builder keys are issued by Bento ops, not this form. Contact the team if you need a mainnet key after the hackathon.