chat completions
tool judged 50% likely a named technique or architecture
See how it has spread across media tiers
Mentions over time
Table view
| Week | Articles | Sources |
|---|---|---|
| 2026-W02 | 1 | 1 |
| 2026-W11 | 1 | 1 |
| 2026-W25 | 1 | 1 |
| 2026-W30 | 1 | 1 |
| 2026-W31 | 1 | 1 |
| 2026-W34 | 1 | 1 |
| 2026-W37 | 2 | 2 |
| 2026-W40 | 13 | 3 |
| 2026-W41 | 2 | 2 |
In their words
configs = { " openrouter " : { " url " : " https://openrouter.ai/api/v1/chat/completions " , " key " : os .
chat_completions ( " Qwen/Qwen3.8-27B-FP8 " , page_classification_messages , max_completion_tokens = 16 , ) label = shadow [ " choices " ][ 0 ][ " message " ][ " content " ] Entity tagging uses the native SDK's extract call with a label list, and relevance judging uses score , as the SIE docs show.
Example Request curl -X POST https://api.unorouter.com/v1/chat/completions \ -H "Authorization: Bearer YOUR_API_KEY" \ -H "Content-Type: application/json" \ -d '{ "model": "gemini-3.6-flash:free", "messages": [ {"role": "user", "content": "Write a short story about a brave cat."} ], "temperature": 0.7, "max_tokens": 150 }' Response The API returns a JSON object: { "id" : "chatcm_12345" , "object"
Where the model sits The model is reached through an OpenAI-compatible chat-completions client behind an interface, which the README says makes the workflows testable without a model.
""" response = requests.post( "https://api.ai-provider.com/v1/chat/completions", headers={"Authorization": "Bearer YOUR_API_KEY"}, json={ "model": "gpt-4o", "messages": [{"role": "user", "content": prompt}] } ) if response.status_code == 200: content = response.json()['choices'][0]['message']['content'] try: return json.loads(content) except json.JSONDecode
The first is an inference server that exposes the API the harness speaks: chat completions, Responses, or Anthropic Messages.
The first version everyone builds Here is the whole failure, in one endpoint: SESSIONS: dict[str, list] = {} SLOTS = asyncio.Semaphore(int(os.environ.get("CONCURRENCY", "32"))) # one pool @app.post("/v1/chat/completions") async def chat(req: Request): body = await req.json() sid = req.headers.get("x-session-id") or body.get("user") async with SLOTS: # everything shares it history = SESSIONS.setdef
This applies to harnesses that resend visible history, typically over Chat Completions or Messages-style APIs.