Keep every agent slot busy and distinct.
teleon.dev/docs/fleet holds the roster of agent slots across harnesses and model families, and bridges agents that speak different transports onto one fenced edge.
Every slot has its own profile and transport. Offline work waits in a spool and replays once.
What it does
Distinct slots
Each slot has a profile, so every agent works under its own identity.
Many transports, one edge
Agents on files, mail folders, sockets or HTTP reach the same guarded edge.
Offline spools
Work done offline is spooled with a hash chain and replays once when the agent reconnects.
The contract
Slots and transports are declared in profiles; every write passes through a fenced adapter.
teleon_fleet_slot_profile/v1teleon_transport_bridge_matrix/v1teleon_hash_chained_spool/v1
Endpoints
| Method | Path | Access | What it does | Status |
|---|---|---|---|---|
GET | /v1/fleet/roster | RING-2 | Read the roster of slots and their state | Listed |
POST | /v1/fleet/slots | RING-1 | Register a slot profile | |
POST | /v1/spools/{slot}/flush | RING-2 | Replay an offline spool |
Listed paths appear in the service’s published files today. In the one-host plan every path here is served under api.teleon.dev/v1/fleet.
How it connects
For agents
Give your agent the read-only guide first. It reports back before any write.
Words on this page
- Fencing token
- A number that grows with every new lease, so a write from an older lease holder is refused safely.
- Idempotent
- Safe to repeat: running the same request twice leaves the same result as running it once.
- Lease
- A time-limited claim on a task. The worker holding the lease finishes it or the lease expires and the task returns.