Invite-only access

Anyone can create an account. Permission to send requests is granted in small groups.

What you can do straight away

Create an account and explore the console.
Create, rotate and revoke API keys in the console.
Read the documentation and prepare your integration.
See the model catalogue and the prices.

What needs access granted

The whole /v1 API. Not just completions — every endpoint under /v1 requires access, including model discovery, the API-key endpoints, usage and billing:

GET /v1/models
POST /v1/chat/completions, streaming or not
All five /v1/api-keys endpoints
All four /v1/usage endpoints
All three /v1/billing endpoints

Requests to any of them are refused with 403 and code beta_access_required:

JSON

{
  "error": {
    "message": "This account does not currently have access to this API.",
    "type": "access_denied",
    "param": null,
    "code": "beta_access_required"
  }
}

The console still works

Key management, usage and billing remain available in the console while you wait. It is the programmatic /v1 surface that is gated, so you can prepare an integration and hold credentials before access arrives.

What a refusal means

Retrying will not help, and neither will a different key. A key proves who you are; it never grants permission.
Nothing is charged. The refusal happens before any hold is placed, before a request is recorded, and before anything reaches a model.
The message is the same for every reason. Not yet invited, not yet activated, terms not acknowledged, or access paused all answer identically — the difference is ours to know, not something the API will tell an unauthenticated-adjacent caller.
401 and 403 mean different things: 401 is "we do not know who you are", 403 is "we know, and the answer is no".

When access is granted

Nothing on your side changes. Existing keys begin working on the very next request — there is no cache to expire and no key to re-issue. If access is later paused, they stop just as immediately, and start again if it is restored.

Checking your standing

Your current access state is on the access page. You can request access from the access request form.

Why it works this way

Access is granted in small groups so that each account's usage can be watched closely while the platform is young. It is a limit on how many people we admit at once — not a limit on what the software does.

Limits while in the rollout

Accounts in the current group carry daily request and spend caps and a restricted model list. They are visible in your console, and they apply on top of your balance and any per-key limits you set. See Rate limits and spend limits.

Model access → Which models you can call. Getting help → When something is wrong.