Docs · how Spiron works
An AI agent that finishes the job.
You hand Spiron an objective. It works on its own for as long as the job needs, keeps you posted, asks only when a decision is genuinely yours, and delivers a result with a record of what it did. This page explains how that works.
- Product
- Spiron
- Website
- https://spiron.ai
- API
- https://api.spiron.ai
- Channels
- Telegram · web chat · API
On this page8 sections
What Spiron is
Work that gets done, not just described.
Most assistants answer questions. Spiron completes work: a refund is issued, a document is read, a customer is answered — and each action is checked against the system it changed.
A job can take seconds or weeks. If a server restarts, a model provider has a bad day, or a task has to wait for someone to reply, Spiron picks up where it left off. Nothing is lost and nothing is done twice.
At a glance
What you hand over, and what comes back
- You hand over
- An objective, what “done” looks like, and a budget.
- Spiron keeps track of
- The objective, progress, waits, attempts, and every action taken — even across restarts.
- You get back
- The finished result, plus a record of every important action.
- It will not
- Call a job done just because a chat ended or a step reported success.
How a job runs
From objective to finished result, in six steps.
The same steps apply to a two-minute question and a month-long project.
Objective
You say what needs to happen, how you will know it is done, and how much it may spend.
Look things up
Spiron searches the knowledge, tools, and systems it has been given access to. What it finds is checked before it is trusted.
Focus
Only the information the next decision needs is used, so large workspaces stay fast and focused.
Act
Spiron acts only through the tools you allowed, within your permissions and your budget.
Confirm
Every important action is checked against the system it changed. If something did not stick, it is reported as a failure — never quietly counted as success.
Deliver
The job ends when your definition of done is met, and you get the result with its evidence.
Job status
Always know where a job stands.
Every job has a clear status you can see in your dashboard.
| Status | What it means for you |
|---|---|
| Queued | Accepted and about to start. |
| Working | Spiron is working on it right now. |
| Waiting | Waiting on a person, a schedule, or an outside system. It resumes by itself. |
| Needs you | Something only you can decide. The reason is stated plainly. |
| Done | Finished, with its evidence attached. |
| Failed | Could not be completed. You see why, and nothing is retried silently. |
| Cancelled | Stopped by you or by a rule you set. |
| Reversed | An action was deliberately undone, and the undo is recorded too. |
Where you use it
One product, three ways in.
The same agents, memory, and records, whichever way you reach them.
| Where | Address | What it is for |
|---|---|---|
| Website | https://spiron.ai | Learn about Spiron, see prices, and create an account |
| Dashboard | The same site, after you sign in | Set up agents and see conversations, memory, spend, and records |
| API | https://api.spiron.ai | Connect Spiron to your own software |
Action records
Proof, not promises.
Every important action produces a record: what was attempted, what the other system reported back, and what actually changed.
Action record · example
job_example_0001
- Action
- Send a message on Telegram
- Attempt
- 1 · completed
- Confirmed by
- Telegram delivery report
- Result
- Delivered to 1 recipient
- Workspace
- acme-example
- Outcome
- Accepted
A chat log is not proof
A conversation describes the work. The action record shows it happened. If a record is missing or failed, the job is not marked as done.
Memory
It remembers, and you stay in control.
Memory belongs to your workspace and survives restarts, retries, and long waits.
- Scoped to you
- Memory is kept per workspace, and can be scoped to a customer, a team, or one agent.
- Editable
- People can correct or delete any memory entry. The change applies on the next turn.
- Survives interruptions
- A crash, a retry, or a wait of days keeps the same objective, progress, and permissions.
- Deletion that sticks
- When you erase data, in-flight work is stopped first so nothing can write it back.
Channels
Where the work meets people.
One agent can answer on several channels, with the same memory and rules everywhere.
| Channel | How it connects |
|---|---|
| Telegram | Connect your Telegram bot in the dashboard. Your bot token is stored encrypted and never shown to the AI. |
| Web chat | Chat with your agent in the Spiron dashboard. No setup needed. |
| API | Call https://api.spiron.ai from your own software. |
Read next
Pick the page that answers your question.
Each page stands on its own.
Next step
Set up your first agent.
The quickstart takes under two minutes: sign up, send your Assistant one line, read its reply.