Accessible model catalog

Use GET /v1/models to populate the canonical model selector for your integration. It returns only model identity metadata, not your commercial terms or project budget configuration.

curl 'https://api.b2b-llm.com/v1/models' \
  -H "Authorization: Bearer $B2B_API_KEY"

Response contract

{
  "object": "list",
  "data": [
    {
      "id": "minimax-m3",
      "object": "model",
      "created": 1784882385,
      "owned_by": "MODEL_OWNER"
    }
  ]
}

The ID and timestamp above illustrate the format rather than company availability. Every entry contains exactly four fields: id (canonical string), object (model), created (stored Unix seconds) and owned_by (configured owner). With no accessible models the data value is an empty array.

MODEL_OWNER is an illustrative placeholder for the configured model owner, not a value to send in a request and not the company workspace brand. Use the actual owned_by returned by the API.

Migration to the minimal catalog

Version 12.0.0 removes the previously expanded metadata from public model discovery and single-model reads. The expanded format is temporarily disabled; ?view=extended, ?view=details and similar query options cannot restore it. Clients depending on capability flags, aliases, context limits or rates must change their configuration source before rollout. Clear old catalog caches after upgrading.

The company workspace Models and prices page has separate text, image, audio and video lists. Each usable media route shows its supported request parameters, options and limits from the current reviewed contract, alongside its account-level tariff. Company/project-key eligibility and Usage Limit valuation must still be checked for the intended key through Playground and the corresponding media catalog/quote. Do not interpret a missing field as a free price, unlimited model or disabled capability.

Aliases agreed for your deployment continue to resolve, including through single-model lookup; discovery returns canonical IDs only. Ask your administrator for an alias when needed rather than assuming it is returned in data.

Organization permissions

Active and frozen keys may read the catalog; a frozen key cannot submit inference. Company model ceilings and existing domain/IP restrictions are unchanged. Employee and project keys inherit the organization's model permissions. Newly excluded models reject execution with company_model_not_allowed, even while a recent catalog response is cached. Prior owned operation results remain subject to their normal access and retention policy.