Read-only snapshots, close to every reader.
teleon.dev/docs/cdn serves content-addressed snapshots and archives from the edge. Search indexes and datasets publish as snapshot files that clients query by range, straight from the nearest edge.
The pointer moves to each new snapshot; old snapshots stay readable by ID.
What it does
Snapshots by content ID
Every snapshot is named by its hash, so caches stay correct.
Query by range
SQLite and DuckDB files answer queries with HTTP range reads.
Close to the reader
Edge caches answer most reads near the agent.
The contract
Snapshots are immutable; a new snapshot gets a new ID and a pointer moves to it.
swh:1:cnt:sha1_git + sha256
Endpoints
| Method | Path | Access | What it does | Status |
|---|---|---|---|---|
GET | /snapshots/{name}/latest.json | RING-3 | Find the current snapshot for a name | |
GET | /s/{swhid}.sqlite | RING-3 | Read a snapshot by range |
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/cdn.
How it connects
For agents
Give your agent the read-only guide first. It reports back before any write.
Words on this page
- Edge
- Servers close to the reader that answer requests quickly and pass the rest to the origin.
- Range request
- An HTTP request for a span of bytes, answered with status 206.
- SWHID
- Software Heritage identifier: a permanent ID made from a file's hash, such as swh:1:cnt: followed by 40 hex digits.