Spot defect patterns across recalls, early.

teleon.dev/docs/recalls gathers CPSC, NHTSA and EU Safety Gate recalls and clusters them with class-action filings that describe the same defect. Each record carries its source, license and read time.

v42.0teleon.dev/docs/recallsRecall feedhttpsjson

Read the docs Copy the agent prompt

One defect cluster

CPSC recallpower bank, 2026-09

EU Safety Gatesame cell, 2026-10

Class actionfiled 2026-10

shared component and failure mode

Cluster: cell overheating3 sources, 1 component

Three records from three sources name the same cell and failure, so they join one cluster that a keyed watch can follow.

What it does

Three recall sources

Consumer product, vehicle and EU market alerts arrive with the product, the hazard and the remedy.

Defect clusters

Records that share a component and a failure mode join one cluster, across sources and countries.

Class actions linked

Court filings that allege the same defect join the cluster, so legal and safety signals read together.

The contract

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

StoreS189

Versionv42.0

SourcesCPSC, NHTSA, EU Safety Gate, class actions

Each recordSource, license, read time

Identifiers

NHTSA campaign number
EU Safety Gate alert number

Execution contracts

Request and responseCopy

GET https://api.teleon.dev/v1/recalls/records?cluster=cl_cell_overheat

# Response
{
  "cluster": "cl_cell_overheat",
  "component": "lithium-ion cell, 21700 format",
  "records": [
    {"id": "rc_cpsc_26_014", "source": "CPSC recalls",
     "license": "public domain", "read_at": "2026-10-24T15:02:00Z"},
    {"id": "rc_eusg_a12_0451_26", "source": "EU Safety Gate",
     "license": "CC BY 4.0", "read_at": "2026-10-24T15:04:10Z"},
    {"id": "rc_ca_docket_8812", "source": "court docket",
     "license": "public record", "read_at": "2026-10-25T09:30:00Z"}
  ]
}

Endpoints

Method	Path	Access	What it does
`GET`	`/v1/recalls/records`	RING-3	List records by source, hazard and cluster
`GET`	`/v1/recalls/records/{id}`	RING-3	Read one record with its source, license and read time
`GET`	`/v1/recalls/changes?since={cursor}`	RING-3	Read every change since a cursor, in order
`POST`	`/v1/recalls/watches`	RING-2	Watch a component, a maker or a cluster 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/recalls.

How it connects

Reads from

Foragerteleon.dev/docs/forager Court docketsteleon.dev/docs/dockets

Feeds into

Catalyst fusionteleon.dev/docs/catalysts Supply chainteleon.dev/docs/supplychain Searchteleon.dev/docs/search

Queuesaq526-aq600

StoresS189 Recalls and Defect Clusters

For agents

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

Agent prompt

Read https://teleon.dev/docs/recalls.md and list the open defect clusters with the recalls behind each. Read only.

Copy

llms.txt Agent card

Words on this page

Full glossary

Defect cluster: A group of recalls, complaints or court filings that share a component and a failure mode.
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.