Your organization workspace

Start with Quick start or open the account guide for the shortest path to your first request.

B2B LLM separates application traffic from the people administering it. A company owns the wallet and pricing arrangement. Projects collect related credentials and enforce a shared usage ceiling. Employees receive access to the projects they need rather than unrestricted access to the company account.

First successful request

After account verification and company activation, open API Keys and Playground. Select an active project key, an available model and a matching protocol. Use a short non-sensitive prompt for this first billable check. A successful HTTP response confirms connectivity; request history provides the corresponding accounting record.

An employee with developer access may select a shared project key in Playground even when another member created it. The temporary browser token uses that employee's execution permissions. It does not expose the original reusable secret or the owner's wallet. Viewer and billing permissions alone do not authorize inference.

Operational boundaries

The company owner and authorized administrators manage people and policies. A project administrator manages project credentials. A developer executes requests within the assigned project. Wallet visibility is a separate company-level permission; being able to view project usage is not the same as being able to read the company balance.

Frozen projects and keys cannot start new inference work. Exhausted budgets also block admission, while a request already admitted can finish and settle its full charge. Set limits with concurrency in mind rather than treating them as prepaid reservations.

Use the workspace Support section for activation questions, access problems and request investigation. Include a request ID and time range, not a full credential or confidential prompt.

Keeping up with support

The workspace displays a compact Support link and conversation count when a new answer awaits reading. Company managers keep their normal organization-scoped access; an employee does not gain access to colleagues' tickets through this indicator. Reading a conversation acknowledges only the messages loaded in that view, and each reader has an independent receipt. Merely opening the Support index leaves the indicator in place. New tracking starts at deployment rather than guessing who read older correspondence.

For company image work, open Playground Images with a permitted project key. Reviewed image contracts and actual employee rights apply; accounting submission and later company-wallet/project-quota settlement remain distinct.