Skip to main content
Agentium connects models to your application’s tools, data, and workflows. Start with a single agent, then add the packages you need for reusable harnesses, APIs, background jobs, browsers, voice, or devices. New to Agentium? Get a working project first. You can choose your application’s architecture after you have seen a run succeed.

Create a new project

Scaffold a TypeScript app, configure a model, and get your first response.

Add to an existing app

Install core and run an Agent in your own project.
Prefer to explore without an API key? Try the controlled-workflow demo: approve or deny a simulated refund using @agentium/harness.

Learn the essentials

1

Understand the pieces

2

Build something useful

Follow the support assistant tutorial: tool calls → conversation state → retrieval → approval → streaming → HTTP. Each checkpoint is a complete program.
3

Make it dependable

Add a repeatable quality gate, inspect traces, and follow the shipping path for your deployment.

Find your application path

Assistants and APIs

Answer from your data, call tools, return structured output, and serve requests.

Harnesses and automation

Compose abilities and controls around agents, teams, or workflows.

Voice and phone applications

Choose speech, media transport, and call control as separate parts of one application.

Background work

Deliver queued jobs, schedule work, and choose a recovery contract.

Browsers and workspaces

Operate web interfaces and configure local or remote execution environments.

Device applications

Connect hardware toolkits, local models, runtime monitoring, and cloud synchronization.

Add only what your application needs

Start with @agentium/core. Add the standalone @agentium/harness for reusable execution capabilities, transport for APIs, queue for background delivery, browser or edge for environment access, and eval and observability for feedback. CLI scaffolding and admin configuration management round out the ten packages. Voice, telephony, memory, retrieval, toolkits, and durable primitives belong to core. Find their boundaries in the package guide, named adapters in Integrations, and exact contracts in Reference.