# Developer Console

> console.curriculo.me is where a Curriculo API account starts and is managed: sign-in, API keys, the product catalogue, usage, billing and support.

**Source:** /docs/console/ (Curriculo Docs)  
**Updated:** 12 October 2026  
**Contact:** hello@curriculo.me

[console.curriculo.me](https://console.curriculo.me) is where an account starts and where it is managed. Everything about the account itself (keys, usage and billing) lives here, not in the API.

| In the Console | What it does |
|---|---|
| **Sign-in** | Creates the account on first sign-in, provisions the API identity your keys will serve, and adds a one-time $5.00 free credit. Until provisioning completes, keys are issuable but calls return `403` "Account provisioning incomplete". |
| **API keys** | Create, name, list and revoke keys, with an optional expiry on each. Up to 25 active keys per account. The plaintext key is returned exactly once at creation; only a prefix and a SHA-256 hash are stored, so a lost key is replaced rather than recovered. Revocation is immediate. |
| **Products** | A read-only catalogue of the available operations. Every operation uses the same account key and the same prepaid balance, so there is nothing to enable or request. |
| **Usage** | Calls, errors, p50 latency and estimated charge, as a summary and a daily time series, filterable by product and by key. |
| **Billing** | Credit balance, card payment through Stripe, and optional automatic top-up below a threshold you choose (off by default). |
| **Documentation** | A copyable cURL request for each operation, which you can also import into Postman. |
| **Support** | In-Console support chat. |

## Why the API key cannot manage the account

Your API key does hiring work. It deliberately cannot mint keys or change billing, so a leaked key can never escalate into account control.

> [!NOTE]
> Every Console view is scoped to your signed-in account. No request accepts an account identifier from the caller, so one account can never read another's keys or usage.

## Separate keys per environment or team

The Usage view filters by key. Issue separate keys for each environment or team to keep spend attributable and each key independently revocable.

See [Authentication](/docs/authentication/) and [Pricing and billing](/docs/pricing/).