Open huge archives one member at a time.
teleon.dev/docs/archives reads only the tail of a large ZIP to list its members, then extracts the one member you need by byte range, checks its CRC and chunks it for storage.
Two small range reads replace one huge download.
What it does
Directory first
The end of the archive lists every member and its offset.
One member out
A single member is inflated from its byte range.
Checked and chunked
CRC-32 is verified and the bytes are chunked into the content store.
The contract
A probe returns the member list; an extract returns one member's content ID.
http_206_eocd_range_sliceteleon_surface_corpus_request/v1
Endpoints
| Method | Path | Access | What it does | Status |
|---|---|---|---|---|
GET | /v1/members | RING-2 | List members from the archive's tail | |
POST | /v1/extract | RING-2 | Extract one member 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/archives.
How it connects
For agents
Give your agent the read-only guide first. It reports back before any write.
Words on this page
- Range request
- An HTTP request for a span of bytes, answered with status 206.
- FastCDC
- Content-defined chunking: files split at points chosen by their bytes, so a small edit changes few chunks.
- CAS
- Content-addressed storage: every file is stored and fetched by a hash of its bytes, so identical bytes are kept once.