Skip to main content
Model Distillation exposes two public HTTP surfaces. Both authenticate with a Forge API key, but they have different responsibilities and tenancy controls.

Management API

The UI uses this same API. Resources are durable and asynchronous operations usually return 202 Accepted with a queued, building, running, or pending state. Poll the resource’s GET endpoint rather than holding the request open. The optional Forge-Entity header selects an accessible team. Resource paths and bodies don’t repeat entity ownership.

Inference proxy

Use an OpenAI SDK with the proxy base URL. The OpenAI-Project: <entity>/<project> header selects the team and project, and the OpenAI SDKs send it from their project option. With the header, model set to "router" uses the project’s weighted routing, and a {provider}/{model} value overrides the model within the project. metadata["forge.project_version"] selects a project version, and omitting it selects version 1.

Interactive endpoint pages

The endpoint pages in this section are generated from the checked-in OpenAPI 3.1 specifications. They include request builders, schemas, response codes, and copyable examples for both surfaces.

Management API

Manage providers, projects, datasets, fine-tunes, evaluations, routing, and analytics.

Inference proxy

Send OpenAI-compatible Chat Completions requests through projects or registered providers.
Agents can start with llms.txt and use the Management API reference or Inference proxy API reference for endpoints, schemas, and examples.
The playground sends real requests. Creating datasets, fine-tunes, and evaluations can consume inference or training resources; routing writes can change production traffic.
Last modified on November 3, 2026