Tenvor documentation
Make your first request
The browser Playground is the shortest path from an invited account to a result. You can use your managed session without creating an API key.
Content checked . Live limits and prices can change.
1. Confirm access and available balance
Follow the existing instructions in your alpha invitation. Sign in to Console and inspect your available balance. Account creation alone does not guarantee alpha access, funded inference or a free trial.
If you need funding or access, follow the instructions currently shown in Console and your invitation. Check alpha status before a test. Never copy payment addresses from an old guide.
2. Estimate one small request
- Open Playground and choose a model currently listed in the live catalog.
- Start a fresh conversation with no private project, attachments or tool history. Enter the short prompt below.
- Set the maximum output to 64 tokens if that is within the model's current published limit. This is an example budget, not a new service limit. If needed, choose a smaller supported value.
- Review the displayed estimate and reservation before sending. A calculator estimate does not reserve capacity.
Reply with one short sentence about a blue square.The output budget is a ceiling, not a required answer length. Start with one request; leave longer histories and tool workflows until this succeeds.
3. Send, finish and inspect the receipt
Send the request once and wait for its completed outcome. First text, a keepalive or an open connection is not completion. If the result is pending, use the existing recovery view instead of immediately sending another request.
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.
Understand reservations and receipts · Resolve an incomplete request
4. Connect an external client when ready
Create a programmatic key explicitly in Console for a trusted client. Browser sign-in and API keys are separate. Keep the key out of command history, URLs, source files, screenshots and support messages.
OpenCode setup uses a hidden key prompt and keeps approvals on. JetBrains setup explains the version-dependent endpoint setting. For your own client, follow the API guide.