Regulatory & filings · Live API
Live API
Regulatory & filings

OpenFDA
on the federated graph.

Drug & device API on Gyri's public-data graph — install the federation pack and multihop with Regulatory & filings and your native integrations.

Drug & device API

Federation path

OpenFDA on
the live graph.

OpenFDA
Gyri graph
Workspace stack
Why federation

Public data belongs
on your graph.

01

Isolated CSV exports

OpenFDA alone cannot join CRM deals, Slack threads, and institutional insights — operators rebuild context manually.

02

No cited multihop

Keyword search in one catalog misses typed joins across trials, filings, entities, and your workspace graph.

03

Agents start from zero

Without federation packs, MCP agents cannot traverse public graph types alongside native connectors in one session.

Use cases

Cited multihop
on your graph.

Multihop query

Join OpenFDA with peer public datasets and CRM/comms connectors in one cited federated answer.

Agent context

MCP agents traverse live OpenFDA graph types alongside workspace insights — not a one-off CSV export.

Cross-federation

Multihop with
peer datasets.

Open Targets Graph rollup ChEMBL Graph rollup UniProt Graph rollup MeSH Seeded catalog EFO / MONDO Graph rollup Orphanet Graph rollup Bio KG domain

Install federation packs in Settings, then query OpenFDA alongside native CRM and comms connectors.

Native stack

Join with
your connectors.

Install OpenFDA on Gyri.

Federation pack + cited multihop with your workspace stack.