Skip to main content
The SDK is a set of packages you compose inside your application. Your host owns authentication, domain data, service credentials, and the lifetime of shared resources.

​
Package boundaries

@agentium/core provides the basic runtime, public model/tool/storage contracts, and durable primitives. Toolkits, voice, and telephony have dedicated core entry points. @agentium/harness composes reusable definitions and execution controls through drivers; the core boundary exposes neutral execution services. Transport, queue, browser, edge, evaluation, observability, administration, and CLI integrations have their own packages. Use the package map for exact imports.

​
State boundaries

Conversation storage retains context. Harness canonical history is separate from Agent backing storage. Queue state describes delivery. A durable task store owns task/action state under its recovery contract. An external service owns its own effects and receipts. Choose the state mechanism for the failure it must survive. See recovery; persistence in one layer does not automatically recover another layer.

​
Ownership boundaries

The application decides what it creates and closes, what it borrows, and what it exposes. Registering a tool does not authenticate a user. Assigning a task ID does not authorize access. Closing a request does not undo an accepted remote operation. Use authenticated hosting for identity and resource ownership, execution policy for validated tool decisions, and operations for shutdown and diagnostics.