Regulatory & filings · Crosswalk
Crosswalk
Regulatory & filings

EMA Clinical Data
on the federated graph.

Policy 0070 acquisition on Gyri's public-data graph — install the federation pack and multihop with Regulatory & filings and your native integrations.

Policy 0070 acquisition

Start free trial Domain hub
Federation path

EMA Clinical Data on
the live graph.

EMA Clinical Data
Gyri graph
Workspace stack
ClinicalTrials.gov
AACT
OpenAlex
Why federation

Public data belongs
on your graph.

01

Isolated CSV exports

EMA Clinical Data 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 EMA Clinical Data with peer public datasets and CRM/comms connectors in one cited federated answer.

Agent context

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

Cross-federation

Multihop with
peer datasets.

ClinicalTrials.gov Seeded catalog AACT Graph rollup OpenAlex Seeded catalog PubMed Seeded catalog Wikipedia Seeded catalog Google Scholar Live API Scholarly domain

Install federation packs in Settings, then query EMA Clinical Data alongside native CRM and comms connectors.

Native stack

Join with
your connectors.

Slack
Notion

Install EMA Clinical Data on Gyri.

Federation pack + cited multihop with your workspace stack.

Start free trial All public data