Org Models Directory

The Models page in the dashboard (Organization → Models) lists every model your organization can route to in a single directory: the full LLM Gateway catalogue plus the models defined for your own custom providers. It answers two questions for your whole team:

• What can we call? — every catalogue and custom model, searchable and filterable by capability, provider, price, and context size, exactly like the public models page.
• What are we allowed to call? — when a provider compliance policy is active, each provider mapping is marked eligible or blocked using the same fail-closed evaluation the gateway applies at request time.

Who can see it

Every active organization member can browse the directory read-only — including project-scoped developer members, who see it as their only organization page. This is the recommended way for developers to discover available providers and models without being granted additional permissions. Management actions (custom-model catalog, attestations) remain restricted to organization owners and admins.

Custom models in the directory

Custom models appear alongside catalogue models, addressed as {customProvider}/{modelName} — the exact model string to send to the gateway:

curl -X POST "https://api.llmgateway.io/v1/chat/completions" \
  -H "Authorization: Bearer $LLM_GATEWAY_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "model": "internal-vllm/llama-4-maverick",
    "messages": [{ "role": "user", "content": "Hello!" }]
  }'

Their pricing, context and output limits, and capability flags come from the custom model catalog. A Source filter switches between catalogue models, custom models, or both.

Compliance eligibility

With an enabled compliance policy (Enterprise), the directory evaluates every provider mapping against the policy — certifications, data-policy requirements, country restrictions, and provider/model allow and deny lists:

• Blocked mappings render greyed out with a ban icon; its tooltip lists the exact failing requirements (for example "No SOC 2 Type 2 report" or "Not on the allowed-providers list").
• Custom providers are evaluated against their compliance attestation; without one on file they are blocked while a policy is active.
• An Eligible only filter narrows the directory to models the gateway will actually route to.

Discover models with an API key

Call GET /v1/models with your API key to list models available under your organization's compliance policy, inherited team and member IAM rules, and the key's own IAM rules. Blocked provider mappings are omitted; models with no remaining mappings are omitted too. Pricing and capabilities reflect the remaining mappings. Accessible custom models use {customProvider}/{modelName} IDs.

curl "https://api.llmgateway.io/v1/models" \
  -H "Authorization: Bearer $LLM_GATEWAY_API_KEY"

The endpoint also accepts the x-api-key header. Without either authentication header, it returns the public catalogue. Invalid, inactive, or expired credentials return 401.

Set ?include_restricted=true to return the full public catalogue even with an authenticated API key. This skips organization, team, member, key, project, and plan filtering for discovery. Private custom models are omitted. Other query filters still apply, and inference requests still enforce all access restrictions. The default is false, which keeps authenticated results filtered.

Use ?mapped=true for provider-prefixed entries. Existing query filters, including no_training, apply alongside access restrictions. Discovery reflects model permissions and project configuration; it does not check remaining credits, usage budgets, or current provider health.

Related

• Knowledge base → Models — a walkthrough of the page itself.
• Custom Providers — bring your own OpenAI-compatible endpoints and define their model catalog.
• Compliance — configure the provider compliance policy.