Skip to content

Have an AI agent? Let it explore Teleon for you. Any assistant works, personal or coding.

Connect your agent
What your agent reads

The request it copies

Explore teleon.dev for me and report back. Read https://teleon.dev/llms.txt, https://teleon.dev/.well-known/agent-card.json and https://teleon.dev/.well-known/mcp.json. Summarize the shared backend primitives at https://teleon.dev/docs and the THP v1.0 connection steps at https://teleon.dev/connect. Stay read-only.

Discovery files on teleon.dev

Read-only discovery is open. Keep TELEON_KEY in your own environment.

Teleon
Sign inApply for an instance

Follow a bill from filing to vote.

teleon.dev/docs/legislative follows federal, state and EU bills through committee markups and votes, and links LDA lobbying filings to the bills they name. Each record carries its source, license and read time.

v42.0teleon.dev/docs/legislativeLegislative feedhttpsjson
One bill's path
1Introduced2026-02-03, referred to committeeDone
2Committee markup2026-04-15, 6 amendments adoptedDone
3Reported2026-05-02, on the floor calendarDone
4Floor votescheduled for 2026-11-12Watching
5Signed into lawafter both chambers pass itNext

Each action is a dated record; three LDA filings that name the bill link to its markup.

What it does

Bills at three levels

Federal, state and EU bills arrive with their committees and the date of every action.

Committee markups

Markups record each amendment offered and adopted, so a bill's changes read as a list.

Lobbying linked

LDA filings name clients, issues and bills, and each links to the bill records it mentions.

The contract

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

StoreS184
Versionv42.0
SourcesFederal, state and EU bills, markups, LDA filings
Each recordSource, license, read time
Identifiers
  • bill: congress, type, number
  • LDA filing_uuid
Request and responseCopy
GET https://api.teleon.dev/v1/legislative/changes?since=cur_5e10&bill=sb-101 # Response { "cursor": "cur_5e19", "records": [ { "id": "leg_xs_2026_sb101_a07", "kind": "committee_markup", "bill": "Meridian State SB 101", "action": "reported as amended, 6 amendments adopted", "date": "2026-04-15", "source": "Meridian State legislature site", "license": "public record", "read_at": "2026-04-15T19:01:44Z" } ] }

Endpoints

MethodPathAccessWhat it doesStatus
GET/v1/legislative/recordsRING-3List records by jurisdiction, bill and committee
GET/v1/legislative/records/{id}RING-3Read one record with its source, license and read time
GET/v1/legislative/changes?since={cursor}RING-3Read every change since a cursor, in order
POST/v1/legislative/watchesRING-2Watch a bill, a committee or an issue 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/legislative.

For agents

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

Agent prompt
Read https://teleon.dev/docs/legislative.md and list this week's committee markups, with each record's source and read time. Read only.
Copy

Words on this page

Full glossary
Markup
A committee session where members amend a bill and vote to report it to the full chamber.
LDA
Lobbying Disclosure Act filings: registrations and quarterly reports naming clients, issues and bills lobbied.
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.