Corporate & identity · Live API
Live API
Corporate & identity

GitHub
on the federated graph.

Public engineering context — repos, releases, and OSS signals federated with product docs, Linear issues, and institutional memory.

Public engineering context

Federation path

GitHub on
the live graph.

GitHub
Gyri graph
Workspace stack
Why federation

Public data belongs
on your graph.

01

Isolated CSV exports

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

Agent context

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

Cross-federation

Multihop with
peer datasets.

GLEIF Crosswalk Wikidata Crosswalk SAM.gov Live API npm Live API OpenCorporates Live API OpenSanctions Live API Archives domain

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

Native stack

Join with
your connectors.

Install GitHub on Gyri.

Federation pack + cited multihop with your workspace stack.