Onboarding Guide

​

Set up your account

​

Create your organization

1

Create it

Open the account menu at the bottom of the sidebar, click Create an Organization, enter the organization name, and click Create Organization.

2

Invite your team

Go to Members, click Invite Member, enter one or more email addresses, choose a role for each person, and click Send Invitation. Only Owners can choose a role other than the default; Admins invite with the default role.

​

Create teams

1

Create a team

Go to Teams and click Create Team (Create your first team if you have none). Enter a name, optionally add members, and set the team’s limits and settings. Owners and Admins can create teams.

2

Add people

Open the team’s Members tab, pick the people to add, and click Add to team.

​

Create API keys

1

Create the key

Go to API Keys and click Create key. Give it a name and, in an organization, choose its Owner: the organization or one of your teams. The owner can’t be changed later.To give someone temporary access, such as a contractor or a candidate on a work trial, set an Expiration Date. The key stops working after that date. Leave it empty and the key never expires.

2

Set its limits and settings

The key starts with a copy of its owner’s settings. Adjust them for this key:

• Spend Limits: a Total Spend Limit that never renews, and a Recurring Spend Limit that renews daily, weekly, monthly, or every N days.
• Routing & Rate Limits: preferred, allowed, and blocked models and providers, plus tokens-per-minute and requests-per-minute limits, overall or per model.
• Data Retention: Zero Data Retention and request logging. See Secure your data.

3

Copy the key

Copy the key right away. You won’t be able to see it again.

​

Add credits and auto top-up

1

Buy credits

Go to Billing, click Buy Credits, enter an amount, and click Continue to Payment.

2

Turn on email or text notifications

Automatic top-up needs a way to reach you. Switch to your personal account from the account menu, open Settings, and under Notifications turn on email or text notifications.

3

Turn on automatic top-up

On the Billing page, click Set up next to automatic top-up. Add a payment card, turn on the switch, set When balance drops below (at least $5) and Add this much (at least $25, and no less than the threshold), and click Turn on.

​

Send traffic

​

Use the Responses API and OpenAI format

​

Choose models with model slugs

​

Routing and fallback

1. Match. Only providers that support the essentials your request uses (streaming, tools, structured output, and so on) are considered. Optional parameters a provider can’t honor, such as sampling settings, may be dropped rather than failing the request.
2. Rank. Providers you list in routing.provider.fallbacks come first, in your order, then providers you hold a BYOK key for, then the rest, ordered by your routing.provider.sort preference (performance by default).
3. Fall back. If a provider is degraded, rate-limited, or unavailable, the request moves to the next provider serving the same model instead of failing. For streaming requests, fallback happens only if a provider fails before its stream starts.

{
  "model": "gpt-6.1-terra",
  "input": "Summarize this text",
  "routing": {
    "provider": { "sort": "cost" }
  }
}

{
  "model": "gpt-6.1-terra",
  "input": "Translate to Spanish: Hello",
  "routing": {
    "provider": { "sort": "p50_latency" }
  }
}

{
  "model": "gpt-6.1-terra",
  "input": "Summarize this text",
  "routing": {
    "model": { "fallbacks": ["claude-sonnet-5-5"] }
  }
}

{
  "model": "gpt-6.1-terra",
  "input": "Process this data",
  "routing": {
    "provider": { "whitelist": ["openai", "azure"] }
  }
}

​

Bring your own keys (BYOK)

• Your provider bills you directly, so nothing is taken from your Concentrate balance.
• Your Concentrate token limits don’t apply, only your provider’s. Your requests-per-minute limits still do.
• Usage still appears in your logs and dashboard, marked as BYOK.

​

Use coding tools

curl -fsSL https://concentrate.ai/scripts/install-cli.sh | bash
cn setup     # save your API key
cn claude    # or: cn codex, cn opencode, cn pi

• Run the setup script from the Claude Code guide.
• If you were logged in to Anthropic in Claude Code before, run /logout first.
• Run /status in Claude Code. It should show https://api.concentrate.ai as the API endpoint.

​

Secure your data

​

Zero Data Retention and request logging

• Zero Data Retention (ZDR) sends requests only to providers that support zero data retention. ZDR belongs to a model-and-provider pair, so turning it on means fewer providers are available for some models.
• Request logging is off by default. Turn it on to store each request’s prompt and response so you can read them in Logs when debugging. Every request’s status, tokens, latency, and cost appear in Logs either way. The Model Optimizer also needs logging on, because it tests models on the prompts and responses in your logs.

​

Guardrails and redaction

​

Monitor usage and activity

​

Logs, errors, and the dashboard

• Dashboard shows your spend, requests, tokens, and errors, plus your balance if your role can view billing.
• Logs lists every request you have access to, with its status, model, key, tokens, and cost. Filter by date, status, model, provider, or key, open a request to see its details, or export to CSV. Request and response content is shown only for keys with logging turned on.
• Errors (under Logs in the sidebar) shows failed requests across all your keys: the error rate, the most common errors, and whether they concentrate on one key, model, or provider.

​

Audit log

​

Alerts

​

Go to production

​

Build for production

import os

api_key = os.environ["CONCENTRATE_API_KEY"]

{
  "model": "gpt-6.1-terra",
  "input": "Your prompt",
  "max_output_tokens": 500
}

# response from client.responses.create(...)
print(response.usage.total_tokens, response.cost["total"])

​

Plan capacity with us

• Before you launch, tell us your expected TPM and RPM, your mix of frontier and open-source models, which models you’ll use, and how bursty your traffic is.
• Once your limits are raised and you need much higher capacity, ramp very large workloads gradually, adding 10–25M TPM every 5–10 minutes, rather than going from zero to 100M+ TPM at once.

​

Optimize cost and latency

​

Launch checklist

• Your organization is created, with one Owner and everyone else as Admins, Billing, or Members
• Separate API keys for production, development, and each major workload, each with a spend limit, and an expiration date on temporary keys
• Credits added and automatic top-up turned on
• Requests send model slugs, not provider/model, unless you have a reason to pin
• BYOK keys added for any provider you have credits with
• Zero Data Retention, logging, and redaction set where you need them
• Low balance, balance depletion, key exhaustion, and error rate spike alerts turned on
• Your code reads the key from the environment, sets max_output_tokens, and retries 424, 429, 500, 503, and 504
• For large workloads: capacity planned with us, and a gradual ramp-up

​

Need help?