Old clients and new schemas, both happy.
teleon.dev/docs/lenses translates requests and responses between schema versions in both directions. Extra fields ride along in a passthrough tail and come back intact.
teleon.dev/docs/lensesLenses v2httpsjsonmcp
A v17 request, end to end
Request in v17k = 10, plus a custom field
Lens upk becomes top_k; custom field in the tail
Served in v20current handlers
Lens downtop_k becomes k; tail restored
The request is upgraded, served, then the response comes back in v17 with its extra fields intact.
What it does
Both directions
Each lens upgrades requests and downgrades responses.
Unknown fields kept
Extra fields travel in a passthrough tail and return as they came.
Composable
Lenses chain, so any version can reach any other.
The contract
A lens is a tested pair of functions between two adjacent versions.
LensesOne per adjacent version pair
TailPassthrough for unknown fields
TestsRound-trip checks on every lens
AccessUsed by the API host
Identifiers
teleon_automorph_lenses_request/v1
Endpoints
| Method | Path | Access | What it does | Status |
|---|---|---|---|---|
GET | /v1/lenses | RING-3 | List lenses between versions | |
POST | /v1/lenses/test | RING-1 | Run round-trip tests for a lens |
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/lenses.
How it connects
Feeds into
Delivery queueFor agents
Give your agent the read-only guide first. It reports back before any write.
Agent prompt
Read https://teleon.dev/docs/lenses.md and show the lens from v17 to v20. Read only.
Words on this page
- Lens
- A pair of functions that translate a request or response between two schema versions in both directions.
- Handshake
- The first call a site or agent makes to agree on API version and settings for everything that follows.
- THP
- Teleon Handshake Protocol: how a site or agent negotiates API version and parameters with the backend.