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

See inside new hardware, part by part.

teleon.dev/docs/teardowns links FCC ID filings, die-shot annotations and hardware bill-of-materials costing for each device. Each record names its source, its license and the time it was read.

v42.0teleon.dev/docs/teardownsTeardown feedhttpsjson
One device, three records
FCC ID filingGranted
FCC ID2AXXX-EX100
Bands2.4 GHz and 5 GHz
Die shotAdded
BlocksCPU, GPU, modem, ISP
LicenseCC BY 4.0
BOM costingEstimate
Lines214
Cost$61.40

The filing, the die image and the parts list share one device key, so each new record lands beside the others.

What it does

FCC ID filings

Equipment authorizations bring the grantee, the radio bands and the public exhibits for each device.

Die-shot annotations

Annotated die images mark the blocks on a chip, each image with its own license.

BOM costing

Parts lists roll up into an estimated cost per device, line by line.

The contract

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

StoreS183
Versionv42.0
SourcesFCC ID filings, die shots, BOM costing
Each recordSource, license, read time
Identifiers
  • FCC ID: grantee code + product code
  • BOM line item
Request and responseCopy
GET https://api.teleon.dev/v1/teardowns/records?fcc_id=2AXXX-EX100 # Response { "device": "Meridian handheld EX100", "fcc_id": "2AXXX-EX100", "granted": "2026-09-30", "bands_mhz": ["2400-2483.5", "5150-5850"], "bom": {"lines": 214, "est_cost": 61.40, "currency": "USD"}, "source": "FCC Equipment Authorization System", "license": "public record", "read_at": "2026-10-25T18:22:40Z" }

Endpoints

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

For agents

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

Agent prompt
Read https://teleon.dev/docs/teardowns.md and summarize the newest FCC ID filings with their estimated BOM cost. Read only.
Copy

Words on this page

Full glossary
FCC ID
The ID on radio equipment authorized by the US FCC: a grantee code plus a product code, with a public filing.
BOM
Bill of materials: the parts in a product and their quantities, used here to estimate its build cost.
Cursor
A position in a feed's change log. Reading since a cursor returns everything newer, in order.
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.