Skip to main content

Documentation Index

Fetch the complete documentation index at: https://blank.build/docs/llms.txt

Use this file to discover all available pages before exploring further.

​
Authentication

Blank SDK authentication has two parts: an API key identifies the Blank account, and wallet signatures authorize the Solana transactions that need wallet authority.

​
Get an API key

  1. Sign in to your account on blank.build.
  2. Choose a username if the account does not have one yet. Blank uses this username for tokens launched through your API keys.
  3. Open the user menu, go to Settings → API Keys, and create a key. It will start with sk_blank_....
  4. Copy the key immediately and store it in your secrets manager or server environment. You won’t see it again.
Treat secret keys like passwords. Don’t commit them to git, don’t ship them to the browser, and don’t paste them in screenshots. If a key leaks, revoke it from the same Settings page and create a new one.
You can keep up to three active keys per account. If you hit that limit, revoke an old one before creating another.

​
Use the key in the SDK

Pass the key to createBlankClient() on your server: 
const blank = createBlankClient({
  baseUrl: "https://api.blank.build",
  apiKey: process.env.BLANK_API_KEY,
});
The SDK sends the key to Blank for calls that need account attribution, quota, audit logs, and revocation. The key alone cannot launch a token or control staking. The creator or controller wallet still has to sign the Solana transaction. Each API key can use the full developer API for that account: launches, launch status, signed submit, staking enable/top-up, fee reads, and the Solana manifest. Treat it as full developer access for the account. If one leaks, revoke it immediately from Settings → API Keys.

​
What needs an API key

These SDK methods require a key:
  • blank.launch.create() — builds and submits a launch
  • blank.launch.get() — reads launch status
  • blank.staking.enable() — turns on staking after launch for tokens launched without staking
  • blank.staking.topUp() — adds a creator-funded staking bonus
Tokens launched through the API are attributed to the Blank account that owns the API key. The actual creator wallet is recorded separately as on-chain provenance, so one Blank username can show all tokens launched by that account’s server wallets.

​
What’s public

The Solana manifest and fee-read endpoints don’t need a key; they’re rate-limited by IP. Use them for displaying data, diagnostics, and read-only client-side calls. Don’t use them as a stand-in for auth — they don’t prove who the user is.