GPT-OSS 20B
A compact model contributing an additional perspective to every query.
Candidate responseBuild with answers that have been considered from more than one angle. Three models, coordinated orchestration, and a dedicated evaluation layer. All through one API.
Your application sends the question.
Inference coordinates the rest.
A structured workflow turns your context into a considered response.
Your team integrates once. Inference handles the coordination.
Start with a question. Add code, a language, or reference context.
One request calls three candidate models in parallel.
Three distinct perspectives address the same question and context.
Multiple available answers are evaluated; a single available answer is returned directly.
The strongest acceptable response is selected and delivered to your application.
Each model responds to the same request and supporting context. The evaluation layer reviews the candidates, so your application receives a single selected answer.
A compact model contributing an additional perspective to every query.
Candidate responseA larger model contributing a separate response to the same context.
Candidate responseAn additional model broadening the set of candidate responses.
Candidate responseGeneration and selection have distinct roles. A dedicated review step
assesses the candidate answers before one reaches your application.
When multiple candidates are available, they are reviewed against the original request. A single available candidate is returned directly without evaluation.
Exclude failed, empty, or mismatched responses.
Review correctness, relevance, completeness, and requested format.
Choose the strongest acceptable answer without merging or rewriting it.
Multiple available answers are evaluated; a single available answer is returned directly.
Keep your application stack. Send a question and optional context through a straightforward HTTP request.
Create a platform key, keep it in your server environment, and authenticate your requests. Manage up to 3 keys from one console.
Manage API keysStart with copyable Python and TypeScript examples.
// Run in your backend with a platform API key.
const response = await fetch(baseUrl + "/api/v1/queries", {
method: "POST",
headers: {
Authorization: "Bearer " + apiKey,
"Content-Type": "application/json",
},
body: JSON.stringify({ query, language, code, responseType: "text" }),
});Manage application access, explore the architecture, and find your integration examples.
Python and TypeScript integration. The platform handles the models.
Authorization: Bearer <API_KEY>{
"query": "Identify the failure modes in this implementation.",
"language": "javascript",
"code": "function first(items) { return items[0].name; }",
"url": "https://example.com/docs",
"responseType": "text"
}One selected answer, reviewed for correctness, relevance, and completeness.
Three candidate answers · One final responseWhat to know before your first request.
No. The orchestration layer calls three models in parallel for every query. Multiple available answers go through evaluation; a single available answer is returned directly.
When multiple candidates are available, evaluation checks correctness, relevance, completeness, and format against your original request. Failed calls and null answers are excluded first. A single available answer bypasses evaluation. Text mode returns answer text; JSON mode parses it into structured data.
Yes. Add source code and its language as optional fields, or include documentation text in your query. You can also supply a reference URL. Its contents are not automatically fetched, so include any text the models need.
Each account has an allowance of 10 requests per minute and 100 requests per day, shared across its keys and authenticated API routes. If you reach a limit, the API returns a retry time.
Open the console, sign in, and create an API key. The integration docs include Python and TypeScript examples for sending your first request from your backend. Request history and usage reporting are not available yet.
Bring your question. Let Inference coordinate the answers.