Know when a standard or code changes.

teleon.dev/docs/standards follows IETF RFCs, ISO, IEC and IEEE standards, the NEC and building codes, and records each new edition with what changed. Records hold the identity, edition and change summary, linked to the publisher's text.

v42.0teleon.dev/docs/standardsStandards feedhttpsjson

Read the docs Copy the agent prompt

Recent changes

Body	Document	Change	State
IETF	RFC 9110	obsoletes RFC 7231	Linked
ISO/IEC	27001:2022	replaces the 2013 edition	Compared
NFPA	NEC 2026	new edition	Comparing
ICC	IBC 2024	state adoptions	Watching

Each change becomes a record with its lineage; the NEC 2026 comparison runs clause by clause.

What it does

Editions and lineage

Each RFC keeps its obsoletes and updates links, and each standard its edition history.

Diffs by clause

Electrical and building code editions are compared clause by clause, so a change reads as a short list.

Text stays with its publisher

Records hold metadata and change summaries, each linked to the publisher with its license.

The contract

Every record carries its source, license and read time, and agents follow a document by cursor or with a keyed watch on its number.

StoreS182

Versionv42.0

SourcesIETF RFCs, ISO, IEC, IEEE, NEC, building codes

Each recordSource, license, read time

Identifiers

RFC number
ISO/IEC reference and edition

Execution contracts

Request and responseCopy

GET https://api.teleon.dev/v1/standards/records/std_ietf_rfc9110

# Response
{
  "id": "std_ietf_rfc9110",
  "title": "HTTP Semantics",
  "published": "2022-06",
  "obsoletes": ["2818", "7230", "7231", "7232", "7233",
                "7235", "7538", "7615", "7694"],
  "source": "RFC Editor index",
  "license": "IETF Trust, BCP 78",
  "read_at": "2026-10-25T20:00:00Z"
}

Endpoints

Method	Path	Access	What it does
`GET`	`/v1/standards/records`	RING-3	List records by body, document and edition
`GET`	`/v1/standards/records/{id}`	RING-3	Read one record with its source, license and read time
`GET`	`/v1/standards/changes?since={cursor}`	RING-3	Read every change since a cursor, in order
`POST`	`/v1/standards/watches`	RING-2	Watch a document or a code with a key

Listed paths appear in the service’s published files today. This surface comes from the Teleon Omnibus Codex v1.0 to v50.0, Oct 25, 2026. In the one-host plan every path here is served under api.teleon.dev/v1/standards.

How it connects

Reads from

Foragerteleon.dev/docs/forager Repos and feedsteleon.dev/docs/repos

Feeds into

Signed feedsteleon.dev/docs/feeds Permits and deedsteleon.dev/docs/permits Catalyst fusionteleon.dev/docs/catalysts

Queuesaq526-aq600

StoresS182 Standards and Code Changes

For agents

Give your agent the read-only guide first. It reports back before any write.

Agent prompt

Read https://teleon.dev/docs/standards.md and list what RFC 9110 obsoletes, with the record's source and read time. Read only.

Copy

llms.txt Agent card

Words on this page

Full glossary

Obsoletes and updates: Links in the RFC index: a newer RFC obsoletes the one it replaces and updates one it amends.
Cursor: A position in a feed's change log. Reading since a cursor returns everything newer, in order.
Keyed watch: A standing request made with an API key that names what to follow and delivers each matching change.
Read time: When Teleon fetched a record from its source. It sits beside the source's own dates, so readers can judge how fresh each record is.