Service
A self-hosted platform that runs agents for people and applications through Console and an HTTP API.
Service manages workspaces, access, agent configurations and conversations; workers keep running after clients disconnect. Get started with a local deployment and your first agent.
Start here
| Your situation | Guide |
|---|---|
| Set up Service and get a first response | Deploy and try locally |
| Your team already runs Service | Use an existing platform |
| Call an agent from your application | Connect your application |
Concepts
- Organization and workspace: an organization manages members; each workspace contains its own agents, resources and conversations.
- Agent and revision: an agent has saved configurations; each run uses a selected revision.
- Session, thread and run: a session groups conversations; a thread holds messages; each run advances that thread.
- Provider and environment: providers connect models, tools and sandboxes; a thread can mount an environment for file and terminal work.
Core concepts follows one conversation through these pieces.
How the pieces fit
- A client sends a message. The Service adds it to the thread's inbox and starts a run when the thread is ready.
- A worker executes the run with Harness, saves its progress and streams live output to the client.
- The run returns a result or waits for an approval, client tool result or answer. Waiting requires an explicit resume; ordinary inbox messages remain queued. See Agents, threads and runs to continue the conversation.
Control and worker are roles of one executable; a single process can run both. See Run and maintain.
Guides
- Get started: deploy, connect a model and send a first message; use Console on an existing deployment.
- Identity and access: workspaces, members, API keys and service accounts.
- Agents, threads and runs: configure agents and integrate conversations; Agent Composer can help build them.
- Resources: discover models, tools and connections, skills, environments, memory, and files and webhooks.
- HTTP conventions, API reference and SDKs and CLI: build an integration.
- Configuration, operations, monitoring and settings reference: run a deployment.
Interfaces
Console and the API share one origin; API operations use /api/v1. The a13n-service executable runs the server and operator commands. See the Service specification for accepted contracts.