Skip to content

Core concepts

An Organization is the security and billing boundary. An End User is your application’s end-user identity within that Organization. An End User is separate from the Platform Account and Organization Membership used to log in to Console. Provisioning an End User creates no Console access.

An Organization API Key authenticates the Organization without acting as a User. A User API Key authenticates one End User and its Organization. Each operation declares the accepted key class; supplying another User’s ID does not grant their private resources.

Resource Meaning
AgentTemplate Organization-owned behavior authored and saved by an author, including instructions and declared dependencies. Saving takes effect immediately.
Session An End User’s private conversation. Creation freezes the selected Template and Session settings in its first Configuration Epoch.
Turn One conversation boundary executed by the Full Agent or Realtime Model. Full Agent Turns may incorporate additional requirements while active.
Interaction The saved admission and original execution result for one stable message, cancellation or checkpoint-retry command; messages also record incorporation.

Each Configuration Epoch retains its admitted Template content, digest and Session settings. The Sandbox settings select a logical Profile and a working directory within the Drive. An explicit Template switch starts a successor epoch. Current ownership and model and dependency availability govern execution.

The Session chooses its answer model at creation. When the model is omitted, it uses the active release’s default model if it is served, otherwise the Organization default. Model selection is independent of the Template and can change during the conversation. An active Turn retains its admitted model; a change applies to the next Turn. Adding an available model requires no new Template or edit.

A Session has at most one active Full Agent Turn; completed Realtime Turns do not occupy that slot. New plain-text requirements can steer that Turn; they do not queue a successor. Admission and incorporation are different facts; the original command receipt and execution history provide recovery. Draft output is distinct from a successful final assistant Message.

A device acts through Client Tools that your application declares on a Session and executes. Text Turns and delegated voice Turns can call them.

Uploaded files have a private, fixed fileId. Upload intent and file readiness are separate; select only ready content for a Turn. See files.

See reading Realtime conversation history for transcript metadata, narration and pagination behavior.