Customer FAQ

What is Tokamak?

Tokamak is an AI API router with a customer workspace for keys, organizations, teams, usage, budgets and credit. It connects applications and coding tools to configured providers. The upstream provider supplies the model; Tokamak supplies the access and accounting controls around the request.

Can I use my existing application?

If it supports one of Tokamak's API dialects and lets you configure its endpoint and key, usually yes. Select a model compatible with that dialect and verify the client's required features. Start with Bring your own client. Availability of a model in one dialect does not imply automatic translation into another.

Which models and prices are included?

The operator chooses the exposed catalog and pricing configuration. Use the Setup guide and model list for your deployment. Ask your operator about current commercial terms, limits, support and data handling; repository documentation does not establish a universal price list, free tier or SLA.

Can Tokamak choose the model for me?

Yes, when your deployment enables auto routing. Name the model tokamak/auto. Each request is then served by the cheapest model of your organization's routing policy that should answer it well, and a stronger one steps in when the classifier is unsure or a follow-up says an answer was wrong. See Auto routing.

Can we use our own Anthropic or OpenAI account?

Yes, when your platform administrator switches on bring your own key for your organization. An owner or admin adds the key under Providers. Requests that key serves run on your provider account, are metered at an internal price you set, and are not charged to your Tokamak credit. Your tools and model ids do not change. See Bring your own key.

Do I need an organization if I work alone?

Your personal account uses an organization for billing and governance too. Create a separate organization when you need shared membership and its own credit and settings.

Does switching organization move my key or credit?

No. Browser context changes where you work in the customer app. Existing keys keep their bound billing organization and team attribution, and each organization keeps its own wallet.

Does a team have its own wallet?

A team is inside one organization. It can have a real shared usage budget, but that budget does not create or fund a separate wallet. Team-attributed requests use the key's bound organization for billing.

Why can I read people but not invite them?

Directory reads and management are separate permissions. Members have permitted read surfaces; administrators manage membership. Billing administrators manage credit and limits without automatically gaining member administration. Custom-role creation is disabled; use the supported fixed roles.

Why did I get a 402, 403 or 429?

A 402 commonly means the payer cannot fund the request. A 429 may be a blocking usage limit. A 403 indicates a permission, key-attribution or other explicit refusal; read its code. A 503 is a service-availability failure, not a request to buy more credit. See Error codes.

Where are provider credentials and my data?

Provider credentials remain server-side. Applications send prompts and inputs through Tokamak to the selected provider. Storage, retention, logging and provider processing depend on deployment configuration. Ask your operator for the applicable privacy and retention policy; self-hosting alone does not establish that no request data leaves your infrastructure.

Can my organization see what I work on?

Only if a platform administrator has switched Insights on for your organization. Then its owners and administrators see the timing, tools, models and cost of the coding sessions you launch with tokamak launch, and you see your own on Home. Prompt text leaves your machine only under a second opt-in, prompt summaries: the launch banner says so, and the server keeps each prompt only until it is summarised, at most 72 hours. See Insights.

Can I invite an external colleague?

An authorized administrator can invite an email address. Delivery depends on configured email service; acceptance is tied to the invited account. Your deployment's admission and organizational policies still apply. See Organizations and teams.

What should I share with a new colleague?

Share your customer-app URL, this Introduction, the Quick start, and an invitation when appropriate. Tell them which organization to use and who handles billing and support. Never share your API key or an operator credential.

Before a wider rollout, confirm the deployment's login method, model catalog, email delivery, billing activation and support contact.