Start using Sine Cloud Console with a signed-in account and an organization. Projects group related resources, and API keys provide programmatic access. Neither is required to use Console.
1. Sign in and choose an organization
Open Sine Cloud Console. Your account has a personal organization. Use the organization switcher at the top left to choose an existing team or create a team organization.
If onboarding appears, choose a workspace, review the unified Free plan, and finish onboarding. Free provides basic Agents, Box, and Powers access. It does not add wallet balance or create projects, keys, or running resources. Existing paid, custom, suspended, or expired restrictions still apply.
Team members should confirm the selected organization before working. See Organizations and members for invitations and roles.
2. Choose a task
| Goal | Action |
|---|---|
| Work with an Agent | Open Agents. An owner or admin prepares the workspace; choose an available model, create an Agent, and submit a message in a session. |
| Manage files or run commands | Open Box, prepare the product workspace, then create a specific Lite or Sandbox resource. Sandbox requires an explicitly started runtime window. |
| Use a tool | Open Powers, find a tool, read its input contract, then provide parameters and run it in the playground. |
| Connect to a model API | Open Gateway, choose an available managed route and configure its budget, or ask an admin to add your own provider connection. |
Agents and Box resources can belong directly to the organization. Powers and Gateway do not require a separate instance. Regular members cannot prepare instances or manage keys, but can use existing resources when permissions and runtime conditions allow.
3. Check costs before execution
Open organization Billing to check available credits. Free access, request limits, and calling balance are separate. Managed models, commands, and tool runs may require credits in the organization wallet. Managed Gateway calls also require an enabled budget with monthly and per-invocation reservation limits.
When using your own provider account, check its bill as well. Purchases and subscription credits go directly to the organization fixed in the order. See Balance and usage for purchases and reservations.
4. Inspect results, then connect your application
After execution, check the product’s sessions, execution history, or call records, then use organization Usage and Billing to inspect usage and settlement. Closing the page, losing a connection, or receiving an unknown status does not prove the task did not run.
For automation, an owner or admin creates an API key with only the required products, capabilities, and project scope. Use real resource addresses from the product’s API page or route IDs returned by Gateway.
Product requests use https://sinecloud.dev as their origin.
Resolve a blocked action
- Missing permission: confirm the organization and your role; ask an owner or admin to prepare resources or review access.
- Insufficient balance or disabled budget: check the selected organization’s wallet. Raising a Gateway budget does not add funds.
- Unavailable model, tool, or runtime: read the reason shown in Console. Preparing resources, adding funds, and creating keys do not replace runtime configuration or required platform approval.
- Uncertain result: retain the original request identifier and inspect history or use recovery. Do not submit another task just to check whether the first one ran.