Know about breaking changes before your agent does.
teleon.dev/docs/feeds publishes signed streams of deprecation, security and pricing events. Each event matches the stored components it affects and can queue a repair job automatically.
teleon.dev/docs/feedsCloudEventshttpsjsonmcp
Recent events
| Type | Subject | Affects | Action |
|---|---|---|---|
| deprecation | auth-sdk 2.x | 2 components | Repair queued |
| security | yaml-parser 5.1 | 1 component | Patched |
| pricing | provider tier change | routing table | Updated |
The SDK retirement matched two stored components, so two repair tasks are queued.
What it does
Signed events
Every event is signed, so agents can trust where it came from.
Matched to what you use
Events link to the components and files they affect.
Repairs queued
A matching event can start a codemod or repair task.
The contract
Events follow the CloudEvents envelope with a signature and affected component IDs.
FormatCloudEvents 1.0, signed
StreamsDeprecation, security, pricing
ActionsCodemod and repair tasks
AccessRING-3 to read
Identifiers
CloudEvents v1
Execution contracts
Endpoints
| Method | Path | Access | What it does | Status |
|---|---|---|---|---|
GET | /v1/streams | RING-3 | List event streams | |
GET | /v1/streams/{name}/events | RING-3 | Read events from a stream | |
POST | /v1/subscriptions | RING-2 | Subscribe a component set |
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/feeds.
For agents
Give your agent the read-only guide first. It reports back before any write.
Agent prompt
Read https://teleon.dev/docs/feeds.md and list recent deprecation events. Read only.
Words on this page
- CloudEvents
- An open standard envelope for event data, so feeds from different sources share one shape.
- SWHID
- Software Heritage identifier: a permanent ID made from a file's hash, such as swh:1:cnt: followed by 40 hex digits.