API graph
Your organisation's APIs and the relationships between them — ownership, consumption and shared shapes — drawn from what teams already publish.
The API graph shows your organisation as it actually is: which teams own which APIs, who consumes them, which services sit where, and which shapes those APIs share. It is built from records the platform already holds — a publish, a grant, a team — so it stays true without anyone maintaining it.
Levels, not filters
An organisation's graph at full detail is far larger than any canvas can draw: a single large API can carry over a thousand schemas. So the level control asks the server for a different amount of graph rather than hiding what your browser already downloaded.
| Level | Shows |
|---|---|
| Landscape | Teams, services and domains. Consumption between teams is rolled up, with a count on the arrow. |
| Contracts | Adds APIs, who owns them, who consumes them, and which domains they participate in. |
| Detail | Adds operations and schemas — only around one API you focus. |
Detail is always focused. Select an API and choose Expand detail; the graph adds that API's operations and schemas, the endpoints that carry each shape, and any identical shapes in other APIs.
Reading the graph
- Node types can be toggled on and off — teams, services, APIs, domains, operations, schemas.
- Click a node for its detail; double-click (or press Open) to go to its own page.
- Dashed purple edges connect schemas that are structurally identical across different APIs — the same shape modelled twice, which no single spec can tell you about.
- Animated edges are consumption: someone holds a grant on that API.
What it will not do
The graph draws relationships Spec0 has a record of, and nothing else.
Which APIs a service exposes is not recorded yet. Services therefore appear with their team ownership and their consumption, and the graph says so rather than leaving you to infer that a service exposes nothing. That relationship arrives with deployment reporting.
Where a view is capped for size, it says so — "showing 25 of 37 operations" — instead of quietly showing you a subset.
Where to go next
- Schema registry — the shapes behind the schema nodes.
- Grants — the consumption edges.
- Teams — the ownership edges.
Schema registry
Every component schema across your APIs' latest versions — searchable down to field names, deduplicated by shape, and explorable as an interactive graph per API.
Governance
Org-level API governance in Spec0 — Spectral linting rulesets plus five publish-time policy gates (naming, breaking-change, required fields, versioning, spec sources).