Sine Agents: models and sessions

Sine Agents provides Agent configuration and a session workspace. One Agents workspace can contain multiple Agents and sessions. Use organization-level resources directly in Console without first creating a project, Box, or API key.

Create and run an Agent

Sign in to Console, select an organization, and open Agents.
If no workspace exists, an owner or admin prepares one. It can belong directly to the organization. Preparation creates the workspace without executing work or adding balance.
Create an Agent, fill in its configuration, select a model from the actual model catalog, and save.
Open Sessions, select the Agent, and explicitly submit a message. Create and try opens the session form without sending a request automatically.
Inspect the latest execution round and its completed response, then open Model calls and costs when needed.

The project selector beside the title chooses an organization-level or project workspace. The organization switcher is at the top left. A scope with no service shows setup actions instead of silently using another project.

Choose a suitable model

In environments connected to Gateway, Agents select routes from the organization model catalog. Search by name or route ID. Your signed-in session or an existing API key with Agents access is sufficient; a separate API key with Gateway access is not required.

Managed models: require an available route, applicable budget, and organization balance, and use Gateway’s published prices.
Own-key models: use a provider connection saved by the organization in Gateway; its provider account pays the upstream charges.
Tools, multiple Agents, or hosted execution environments: require a route with confirmed tool support. Text-only sessions without tools and with environment none can use text routes whose tool capability is unknown.

Agents currently needs streaming text responses. Models without that capability, including fixed-request-price models that do not support streaming, show an unavailable reason. If the catalog is empty, check organization and instance access, then inspect connections, route status, and key route restrictions in Gateway.

Renaming an existing Agent or editing its instructions does not migrate its model. To change models, explicitly select and save an available model, then create a new session. Every execution still checks current route permissions and capability limits.

Understand status and costs

An idle session does not prove that its last execution succeeded. Inspect the latest round, response, and any error. A task may make several model calls when the model requests a tool and then answers using the result.

Calls through Gateway have one Gateway billing source; Agents does not charge again for the same model call. Own-key calls currently have zero Cloud service fees, while provider charges remain on the provider bill. The call list is not a total for the whole session or organization. Unknown usage is not zero.

Closing a page or disconnecting the live subscription does not cancel work automatically. Use the session cancellation action to stop work. If the result is uncertain, inspect the original session and call records and retain request and invocation IDs before sending the same task again.

Files, Box, and programmatic access

Existing Agents workspace files remain on the instance’s Files page and do not move automatically into Box. An Agent can explicitly link a Box in the same organization and project scope. This is optional, and both products must pass their own permission and runtime checks.

For programmatic access, use the real instance address and selected-Agent example on the API page. Create an API key with Agents and the required capabilities, using a project scope that matches the resource. Do not invent Agent IDs or use another organization’s resource address.

Resolve blocked execution

Insufficient balance: check organization Billing; members should contact an owner or admin.
Oversized input: shorten instructions, history, or tool definitions, or choose a higher-capacity route and create a new session.
Missing tool support: select a model with confirmed tool support.
Unavailable route, platform configuration, or runtime: retain the request identifiers shown in the error and contact an administrator.