Trials, safety signals and FDA dates together.

teleon.dev/docs/clinical joins ClinicalTrials.gov records, FDA FAERS reports and the PDUFA calendar, so each drug's trials, safety signals and decision dates read together.

v32.0teleon.dev/docs/clinicalTrials feedhttpsjson

Read the docs Copy the agent prompt

Calendar and signals

Date	Sponsor	Event	Source
Oct 21	Meridian Pharma	FAERS reports up 3x	FAERS
Nov 14	Meridian Therapeutics	PDUFA date	sponsor filing
Nov 30	Meridian Bio	Phase 3 readout	ClinicalTrials.gov
Dec 5	Meridian Pharma	Advisory committee	FDA calendar

PDUFA dates and trial readouts share one calendar, and a jump in FAERS reports for a marketed drug arrives as a signal.

What it does

Trials as registered

ClinicalTrials.gov records give each trial's phase, status and completion dates.

Safety signals

FDA FAERS reports are counted by drug and reaction, and sharp rises are flagged.

PDUFA calendar

FDA action dates sit on one calendar with the trials and sponsors behind them.

The contract

An event names its drug, sponsor, kind and date, with the registry, FAERS or calendar record behind it, its license and read time.

StoreS114, added in v32.0

SourcesClinicalTrials.gov and FDA FAERS

CalendarPDUFA dates

RecordsEach record carries its source, license and read time

Identifiers

clinical.event
clinical.faers_signal

Execution contracts

Request and responseCopy

GET /v1/clinical/events?kinds=pdufa,readout&from=2026-11-01&limit=2
Host: api.teleon.dev

# Response
{
  "events": [
    {"id": "ce_6001", "kind": "pdufa", "date": "2026-11-14",
     "sponsor": "Meridian Therapeutics Inc", "application": "NDA",
     "trials": ["NCT00000001"], "source": "sponsor filing",
     "license": "terms:sec-edgar", "read_at": "2026-10-22T10:30:00Z"},
    {"id": "ce_6017", "kind": "readout", "date": "2026-11-30",
     "sponsor": "Meridian Bio plc", "phase": 3,
     "trials": ["NCT00000002"], "source": "ClinicalTrials.gov",
     "license": "terms:ctgov", "read_at": "2026-10-24T02:11:37Z"}
  ],
  "next_cursor": "c_e0b3"
}

Endpoints

Method	Path	Access	What it does
`GET`	`/v1/clinical/events`	RING-3	List PDUFA dates, readouts and safety signals by date
`GET`	`/v1/clinical/events/{id}`	RING-3	Read one event with its trials and sponsor
`GET`	`/v1/clinical/changes?since={cursor}`	RING-3	Stream registry updates and FAERS counts since a cursor
`POST`	`/v1/clinical/watches`	RING-2	Watch a drug or sponsor for dates and safety signals

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/clinical.

How it connects

Reads from

Entitiesteleon.dev/docs/entities Lab spinoutsteleon.dev/docs/spinouts

Feeds into

Catalyst fusionteleon.dev/docs/catalysts Decision marketsteleon.dev/docs/futarchy

Queuesaq261-aq350

StoresS114 Trials, Adverse Events and PDUFA Calendar

For agents

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

Agent prompt

Read https://teleon.dev/docs/clinical.md and list PDUFA dates in the next 60 days with their trials. Read only.

Copy

llms.txt Agent card

Words on this page

Full glossary

PDUFA date: The goal date by which the FDA aims to act on a drug or biologic application, set under the Prescription Drug User Fee Act.
FAERS: The FDA Adverse Event Reporting System: reports of side effects and medication errors filed after a drug reaches the market.
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.
Change cursor: A position in a feed's change stream. A reader sends the last cursor it saw and gets every change after it, in order.