Models
Browse every model your organization can use, with compliance eligibility
The Models page shows every model available to your organization in one directory. When your organization enforces a provider compliance policy, the page also shows exactly which models are eligible — and why the rest are blocked.
Every organization member can browse this page, including project-scoped developer members, so your whole team can see which models are available without needing admin access.
The directory
The directory is the same table you know from the public models page, with one row per model:
| Column | Description |
|---|---|
| Provider | The model vendor (Anthropic or OpenAI) |
| Model ID | The model id; the copy button copies the exact string to request |
| Input / Output $/M | Prices per million tokens (per-request/per-character where applicable) |
| Cache Read $/M | Cached input price where supported |
| Features | Capability icons: streaming, vision, tools, reasoning, JSON output, … |
Search matches model names, ids, aliases, and providers. The Filters panel offers the same controls as the public directory — use case, capabilities, provider, price and context ranges — plus one control specific to this page:
- Eligible only — hide models blocked by your organization's compliance policy.
Lifecycle status
Every model carries exactly one lifecycle status, shown as a badge on the model and selectable from the Status chips in the filter panel:
| Status | Meaning |
|---|---|
| Deprecated | Still available; the vendor has announced a sunset, so migrate soon |
| Scheduled | Still available, but deactivation is set for a date inside the next 90 days |
| Deactivated | No longer available; requests return errors |
Status resolves by urgency — deactivated beats scheduled beats deprecated — so a
model never carries two, and a deactivation further out than the 90-day notice
window stays plain active rather than warning early. The chips are single-select
and write to ?status=, so a filtered view can be shared.
With no chip selected, the directory lists everything available and hides models already past their deprecation or deactivation date.
Compliance eligibility
When your organization's provider compliance policy is enabled, every row is evaluated with the same fail-closed rules Halfbill enforces at request time — data-policy requirements (no training on prompts, zero data retention), vendor certifications, and provider/model allow and deny lists.
Rows that fail render greyed out with a red ban icon; hover it to see the exact reasons, such as "Not on the allowed-models list".
Eligibility marking requires an active compliance policy, available for team organizations on request (hello@halfbill.uk). Without one, the directory simply lists all models. Configure the policy on the Compliance page.
How is this guide?