Every context pack, tool and asset, in one vault.
teleon.dev/docs/files stores context packs, harness files, tools and assets, and bundles them for any harness. Downloads come with checksums, and archives can be read by range before anything is unpacked.
Every file in a bundle carries its checksum. The installer reads and checks them before anything runs.
What it does
Bundles for any harness
The same files ship as folders for Claude Code, Codex, OpenCode or Pi.
Checksums with every download
Each file lists its SHA-256 and SWHID, so installs can verify before running.
Read archives by range
A range probe reads an archive's directory first and lists its members.
The contract
Files are stored once in the content store; the vault keeps names, bundles and permissions.
/v1/creative bundlesswh:1:cnt:sha1_git + sha256http_206_eocd_range_slice
Endpoints
| Method | Path | Access | What it does | Status |
|---|---|---|---|---|
GET | /v1/range/eocd-probe | RING-3 | Read an archive's member list by range | Listed |
GET | /v1/creative | RING-3 | List creative bundles | Listed |
GET | /v1/bundles/{harness} | RING-3 | Download a bundle for one harness | |
POST | /v1/files | RING-2 | Upload a file with a scoped key |
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/files.
How it connects
For agents
Give your agent the read-only guide first. It reports back before any write.
Words on this page
- SWHID
- Software Heritage identifier: a permanent ID made from a file's hash, such as swh:1:cnt: followed by 40 hex digits.
- Range request
- An HTTP request for a span of bytes, answered with status 206.
- CAS
- Content-addressed storage: every file is stored and fetched by a hash of its bytes, so identical bytes are kept once.