Give your app a key

A key lets your app use another service on your behalf. Only you can create it, in your account with that service. crisp never makes up a key.

Which keys crisp asks for#

When a feature needs a key, crisp builds everything around it, shows a "not set up yet" message in its place, and asks for the key by its exact name in its final reply.

Keys live in Secrets, a private list for each project. Your app can read them. The AI that builds your app only ever sees their names, never the values.

Give crisp a key#

1. 1 Create the key in your account with the service, and copy it.
2. 2 When crisp asks for a key, press the Add button under its reply, for example Add RESEND_API_KEY. Or open the More menu in the top bar and choose Secrets.
3. 3 Check the Name, paste the key into Value, and press Save secret.
4. 4 Your preview restarts so the app can use the key. Try the feature in the preview.

Manage your secrets#

• You cannot see a value again after you save it. To change it, press Replace and enter the new value.
• Press Delete to remove a secret. Your app stops getting it, and your preview restarts.
• Names use capital letters, numbers and underscores, such as RESEND_API_KEY. A few names are reserved for crisp, such as PORT and DATABASE_URL.
• Your published app gets your secrets when you publish. After you change a secret, publish again so the live app uses the new value.
• Secrets are never part of your code, so they are not in your GitHub repository.

Keep your keys safe#

• Never paste a key into a page, a form field of your app, or a file in the Code tab.
• Prefer test keys while you build. Stripe test keys start with sk_test_.
• If a key leaks, delete it at the service and create a new one. Then give crisp the new key.