Platform · Allow-listsApproved providers and models, recorded per agent

Approve the models
each agent
can use.

Every agent is bound to an approved provider and carries a list of approved models. A call to another model is flagged, or blocked if you turn blocking on for that agent. Use cases, Obichat workspaces, and access keys narrow that scope further.

01 / What you can approve

Providers. Models. Workspaces. Keys.

Approvals are recorded at four levels, so reviewers can see exactly which provider and models each agent, use case, workspace, and key is meant to use. The agent level is checked on every call.
01 — AGENTS

Approved provider and models

Each agent is bound to an approved provider and has a list of approved models. A call to another model is flagged and let through by default, or blocked if you turn blocking on for the agent. Either way the attempt is recorded on the request trace. This applies to calls made through the agent endpoint.

Per-agent · flag or block
02 — USE CASES

Allowed models per use case

Each use case carries the model IDs allowed for it, per provider, so the approved model set is documented where the use case is registered.

Use case · model IDs · per provider
03 — OBICHAT

Workspace model lists

Each Obichat workspace lists the allowed models for every provider attached to it, so teams chat only with the models their workspace permits.

Workspace · provider · allowed models
04 — ACCESS KEYS

Keys scoped to agents

Access keys can be scoped to specific agents, so a key issued for one agent cannot be used to reach another.

Key · agent-scoped