Prentis One

​

Two modes

​

Connect

import os
from openai import OpenAI

client = OpenAI(base_url="https://compute.prentis.ai/v1", api_key=os.environ["PRENTIS_API_KEY"])
reply = client.chat.completions.create(
    model="auto-open",
    messages=[{"role": "user", "content": "Prove that there are infinitely many primes."}],
)
print(reply.choices[0].message.content)

import OpenAI from "openai";

const client = new OpenAI({ baseURL: "https://compute.prentis.ai/v1", apiKey: process.env.PRENTIS_API_KEY });
const reply = await client.chat.completions.create({
  model: "auto",
  messages: [{ role: "user", content: "Summarise this changelog in three bullets." }],
});
console.log(reply.choices[0].message.content);

curl https://compute.prentis.ai/v1/chat/completions \
  -H "Authorization: Bearer $PRENTIS_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"model": "auto", "messages": [{"role": "user", "content": "Hello"}]}'

export ANTHROPIC_BASE_URL="https://compute.prentis.ai"
export ANTHROPIC_API_KEY="$PRENTIS_API_KEY"
export ANTHROPIC_MODEL="auto"

​

Choosing among models you name

​

What you see in the response

​

When three models answer

• Streaming arrives in one piece. The best answer is only known once all three have finished, so a streamed call receives keep-alive comments (: keepalive) while it waits and then the whole answer, its usage and [DONE] at once. Clients that read SSE correctly need no change; just do not time out on the first byte.
• If one or two of the three fail, the answer comes from those that succeeded. Only if all three fail does the call fail, with UPSTREAM_UNAVAILABLE or UPSTREAM_TIMEOUT.

​

Limits

• 120 seconds per upstream call. Each attempt — and each of the three answers, and the comparison — gets at most 120 seconds. A model that has not finished by then counts as failed. Very long reasoning on the hardest questions can hit this; the overall request deadline still applies on top.
• At most five upstream calls per request, in both modes: a first choice and up to three standbys, or three answers and one comparison. The classification that decides the route is not counted. The same five-call ceiling applies to every request on the platform.

​

Billing

• Tokens are billed at the price of each model that ran, exactly as if you had called it directly. When three models answer, all three answers and the comparison are billed — usually three to four times the cost of a single call. A call still counts as one request. The usage in the response counts the answer you received; the other calls appear only on your usage and billing pages.
• Routing fee. A call Prentis One had to classify carries a small fee: the classifier’s input tokens, currently $0.042 per million (a reference price that may change; you are billed at the fee in effect when each request is made). It shows as its own line under Prentis One. There is no fee when you name a single model with auto:<model>, on a tool-result turn that continues a conversation, or when the classifier could not answer.

​

Known limits

• Prentis One chooses for capability, not for cost or speed.
• Switching models mid-conversation can still lose prompt-cache hits and reasoning continuity.
• On auto-open, a question that needs tools is never answered by three models: it goes to one model, which can call your tools.

​

Next