Skip to main content
1

Configure your Authentication

You’ll need to configure your auth provider’s JWKS endpoint in the Chipi Dashboard. The dashboard quickstart detects your auth provider and walks you through the setup.
With this JWKS Endpoint setup, you can now run secure code in your frontend using a rotating JWT token.

Common auth providers

The dashboard auto-configures JWKS when you provide your Clerk Secret Key.
2

Get your API Keys

Go to the Chipi Dashboard and open your project. The quickstart shows your .env snippet with both keys ready to copy.You’ll need:
  • Public Key (pk_prod_xxxx) — used client-side
  • Secret Key (sk_prod_xxxx) — used by the server-side ChipiProvider
3

Frontend Code to create a wallet

Since this wallet is self-custodial, there are many steps that need to be done in the frontend.Here is the code to create a wallet for your user.
Chipi supports two wallet types:
  • CHIPI (default): OpenZeppelin account with SNIP-9 session keys support
  • READY: Argent X Account v0.4.0
4

Create a Wallet

Now you can create a wallet for your user.
For the bearerToken you need to pass a valid JWT token from your auth provider.

Create a ChipiWallet (Default)

ChipiWallet is an OpenZeppelin account with SNIP-9 session keys support, perfect for gasless transactions and delegated access.

Create a Ready Wallet

If you need Argent X compatibility:
Backward Compatibility: If you don’t specify walletType, the SDK will create a ChipiWallet by default. Existing integrations will continue to work without changes.