---
title: Project settings
description: Get the credentials and app settings required by your SDK integration.
---

[!nav:main](/nav/main.md)

Open your project's **Settings** group for **Keys**, **App verification**, and **Budget & limits**.

## Keys

| Credential | SDK use | Handling |
| --- | --- | --- |
| Public project key | `projectKey` | Safe to include in the app; not a login credential |
| Debug key | `debugKey` for local testing | Secret; never ship in a release build |
| Server key | `serverKey` on a production backend | Server-only secret; never send to clients |

For onboarding, create only an account developer key under **Account → CLI keys**, then run `croche login` yourself after the agent installs the CLI; follow the [quickstart](../quickstart.md). Login is pending release verification; never give the agent your key. In the planned workflow, your coding agent creates the project and has the CLI write the SDK debug key privately to `.env`; you do not copy that secret from Studio. CLI availability and file protections remain pending verification.

For later manual administration, keep any secrets Studio displays in private configuration, never in a repository, screenshot, or AI instructions. Revoke only credentials you intend to stop using.

## App verification

Follow your SDK's reviewed app-verification steps before distributing a production build. React Native uses App Attest on iOS and Play Integrity on Android; see the [React Native guide](../sdks/react-native.md).

A successful simulator or emulator test with a debug key does not verify the production setup. Native [Swift](../sdks/ios.md) and [Kotlin](../sdks/android.md) API instructions remain pending review.

## Check a limit

If a request reports a usage limit, inspect **Settings → Budget & limits** and the relevant [usage view](../concepts/credits.md) before retrying. See the [hackathon guide](../hackathon.md) for event allowances.