Get started

Access tiers

Every organization has one tier. It applies to all of its projects and keys.

Developer Verified Research
Standard models Yes Yes Yes
Abliterated models No Yes Yes
Refusal retry on auto aliases No Yes Yes
Bring your own model No No Yes
Default rate limit (per key) 60 RPM 600 RPM 3,000 RPM
Batches, workflows, Responses, Messages Yes Yes Yes

New organizations start on Developer.

Enterprise is a commercial arrangement on top of a tier: invoice billing with a credit limit and agreed limits. Contact sales.

What each tier unlocks

Developer. Every standard model, the router, batches and workflows. The router always picks standard models. If a standard model refuses, you get the refusal.

Verified. Adds the abliterated checkpoints. You can pin them by id (they end in -abl), force them with the x-utmost-variant: abliterated header, and let the router retry refusals on them. See Routing.

Research. Adds bring your own model. Below Research, the /v1/byo/* endpoints return feature_not_available (403).

Applying for verification

Apply from the dashboard, under Verification. You need a confirmed email address, and an organization can have one pending application at a time. The application asks for:

  • the organization's legal name, primary domain and website;
  • country;
  • the segment you work in (AI safety, trust and safety, security, ML data, research, writing and analysis, or other);
  • a description of your use case;
  • the requested tier (Verified or Research);
  • a signature on the current acceptable use policy (version 2026-11): the signer's full name, recorded with the time.

We check whether the applicant's email domain matches the organization's domain. A person on our trust and safety team reviews every application. You get an email with the decision. Approval takes effect on existing keys right away; there is nothing to rotate.

The acceptable use policy is at /legal/acceptable-use.

The tier_required error

Calling an abliterated model without a Verified organization returns:

{
  "error": {
    "message": "Abliterated checkpoints need a Verified organization. Apply in the dashboard.",
    "type": "permission_error",
    "code": "tier_required",
    "param": null,
    "request_id": "req_..."
  }
}

It is returned when you:

  • pin an abliterated model id, or
  • send x-utmost-variant: abliterated with an auto alias.

Plain auto requests never return it. Without verification the router stays on standard models.

GET /v1/models shows "available": false on models your organization cannot call.