Set up your organisation
The steps an owner or admin takes in the console, before and after a developer connects the first application.
This is the setup you do in the console. One step needs a developer: changing two lines of code so your applications send their AI requests through CoreValue. Everything else happens here.
Sign in and name your organisation
Sign in at app.corevalue.dev. The first time, you are asked to name your organisation. Keys, budgets, requests and reports all belong to it.
Add your provider keys
On Gateway → Provider keys, add a key for each AI provider you use, such as OpenAI, Anthropic or Google. CoreValue uses it to call the provider on your behalf, and the provider keeps billing you as it does today. Your applications never see it. See Provider keys.
Create CoreValue keys
On Governance → Keys, create the keys your applications will use instead of provider keys. How you split them decides how you can split spend:
- One key per service or environment, so each can be capped on its own.
- A team on each key, so spend lands on that team for budgets and chargeback.
- A key scoped to one customer, if you resell AI, so every request on it is counted for that customer.
Each key is shown once, when it is created. See API keys.
Add your team
On Governance → Access, click Invite member and choose a role. Someone who already has a CoreValue account is added straight away. Create teams below the members list, and add people to them. See Members and Roles.
Set a first budget
On Budgets & Limits → Organization, set a Monthly Budget a little above what you expect to spend, with the action Alert only, and add yourself on Notifications → Budget alerts. Nothing is refused while you learn what normal looks like. See Budget configuration.
Hand the keys to your developer
Send your developer the key you created and the developer Quickstart. It is two lines of code: the gateway's base URL and the CoreValue key.
See your first requests
Once requests arrive, Requests lists each one with its model, tokens and cost, and Overview shows spend so far this month. See Overview.
Next
- For SaaS companies: cost and margin per customer.
- For AI-native teams: spend and budgets per team.
Architecture
How a request travels through CoreValue: the ways in, the checks before the provider, how cost and budgets are kept, where data is stored and what happens when something fails.
Key concepts
The words these docs use, in plain English — read this once and the rest of the docs will make sense.