Tenvor documentation
Documentation
Run open-model chat through the browser Playground, OpenCode or an OpenAI-compatible client. Start with a small request, then check its result and receipt.
Content checked . Live limits and prices can change.
Make your first request
Start in the browser with one short synthetic prompt and a small output budget. The quickstart covers access, an estimate, the request and its receipt.
Access and authentication
Follow your existing invitation instructions, sign in, and inspect your available balance in Console. Creating an account does not by itself establish alpha access, funding or available capacity.
Playground uses your managed browser session. Create a programmatic API key in Console only for a trusted external tool; it can spend your prepaid balance.
Tools and IDEs
Use a synthetic or non-sensitive project during the alpha. Coding tools can send files, tool arguments, terminal output and conversation history to independent operators. Keep approval controls enabled.
For OpenCode, check the access and setup requirements, then copy this command into your terminal. Enter your programmatic key only at the setup’s hidden prompt.
curl -fsS https://tenvor.io/setup/opencode.sh -o tenvor-opencode.sh && bash tenvor-opencode.shYou can also select the command and copy it manually.
Set up OpenCode · Set up JetBrains AI Assistant · Invited alpha client checklist
Chat Completions API
The API base URL is https://orchestrator.tenvor.io/v1. Use the documented text and function-tool subset; compatibility does not cover every OpenAI API or every IDE feature.
V10 dynamic streaming can deliver text in committed batches. Updates may arrive in bursts. Clients wait for a complete tool call and a successful terminal outcome before execution.
Assurance is server policy
The server selects the active assurance policy. A client field or a price-calculator selection does not activate a different policy. Successful responses report the actual validation_tier.
Models and limits
Check the live catalog before a request. A model's context window, aggregate input-byte budget and output limit are separate constraints; history and tool definitions also consume input budget.
Estimates and reservations
Check current prices before sending. Admission reserves funds; a reservation is different from a final charge. Use the request's authenticated outcome and receipt to understand settlement.
Verify the result
After completion, check the matching time window, model, usage and charge in Console Activity. A configured endpoint or an answer claiming to be Tenvor is not proof of a completed Tenvor request. If the account evidence is missing or still pending, record the outcome as unverified and reconcile it before submitting again.
Troubleshoot before retrying
A disconnect, HTTP 503 or HTTP 504 alone does not establish whether work was admitted or whether a charge is due. Keep the request reference privately, check the authenticated result and account activity, and reconcile accepted work before retrying. Do not turn a partial answer into a successful completion.