Skip to main content
A builder API key authorizes your application to use protected Renaiss endpoints. Your users keep their own accounts and EOA wallets; you do not need to create Renaiss user API keys for them.

​
Request access

Email info@renaiss.xyz or contact your Renaiss representative with:
  • Your app name and the Gacha, Marketplace or Redeem flows you will support.
  • The environments and networks you need, plus expected request volume.
  • For Redeem, the exact frontend origins where users will sign, including local development ports.
Renaiss provisions the builder key, confirms the API deployment and permissions, and registers the signing origins. For shipping verification, also confirm the canonical wallet-session issuer. Use separate environment configuration for testnet and mainnet.

​
Configure your backend

Store the key as a server secret, for example RENAISS_BUILDER_API_KEY. Send it in x-builder-api-key when forwarding authorized requests to the API. Browser SDK clients should call your backend and omit builderApiKey. See authentication for the credential matrix and proxy requirements. Public catalogs do not require a builder key.

​
Builder attribution

The EOA API derives attribution from the authenticated builder. Do not pass a caller-selected builder code as a substitute for authorization. Changing the builder key can change the scope of wallet history and buyback offers.

​
Limits and execution

Request quotas, permitted flows and sponsored execution depend on your builder configuration. Confirm them during onboarding; builder tiers describes the program. User-sent token approvals still require gas in the wallet, even when the subsequent API action is sponsored.