Skip to content

What are Hardware Agent Services?

Hardware Agent Services let your application offer an assistant for a hardware product. Define its behavior once, save it as a Template, and give each End User private Sessions. The service runs the model, streams its answers, and provides controlled access to tools and files. Your application can give a Session the actions of its owner’s devices as Client Tools.

For example, a robot support assistant can explain setup steps, read an uploaded measurement file, calculate a summary in a Sandbox, and ask the End User’s robot for its status through a Client Tool. Your application presents the conversation and integrates any physical-device transport.

Need What the service manages
Consistent assistant behavior One editable Template whose saves take effect immediately. Each new Session fixes the current content.
Personal conversations Private Sessions with explicit Templates and saved Turn results.
Responsive interaction Streamed progress and answers; new plain-text requirements can steer the active Turn.
Spoken interaction Realtime audio on the same Session, transcripts and Full Agent task progress. See Realtime voice.
Work beyond a text answer Template-enabled tools and a Sandbox, with results returned to the model.
Product-specific inputs Verified private file uploads and selection of ready content for a Turn.
Usage visibility Usage attributed to the Organization and End User, priced at the platform sale price.

Client Tools: Your application or device can declare Client Tools on an ordinary text Session and execute their calls. The platform routes required actions and results; your integration owns device transport and physical execution. Voice device actions delegate to Full Agent Turns, which use the same Session Client Tools; Realtime exposes no direct device or Session-client tools.

Your application owns the End User experience, maps its identities to End Users in the service, keeps API keys on its backend, and integrates physical devices when needed.

Your Organization’s administrators use Console to author Templates and manage policies. Console management identities are separate from End Users.

The service resolves the Session’s current configuration, checks current access, runs Turns and allowed tools, saves results, and reports usage. Your backend calls the public API with the key class accepted by each operation.

  • Product support: reuse one robot support Template across many End Users, while keeping their conversations and files private.
  • Maintenance analysis: let an End User upload measurements and ask an assistant to explain anomalies using the tools enabled for that Template.
  • Hardware-aware assistance: declare the End User’s device actions as Client Tools on their Session, while your own integration controls the device.

A Template defines shared behavior. A Session uses the selected configuration for one private conversation. Architecture shows how those resources relate to each other and to devices. Capabilities and examples shows observable behavior, then Quickstart starts your first conversation.