Recorded corporate control
UK Company Control Graph API
Trace Companies House corporate PSC evidence beyond one company while keeping traversal limits, unresolved identifiers, and source vintages visible in the result.
What it makes possible
A public-record check that keeps its provenance
The separate control graph endpoint follows recorded corporate controllers and, in group mode, bounded controlled companies and shared controllers. Every result carries the nodes and evidence edges it found, the coverage it achieved, and the frontier where discovery or assessment stopped.
01
Check the starting record
The ordinary entity response stays non-recursive. Use ch_psc.corporate_psc_count to identify active corporate PSC records and control_graph_available to confirm that the caller's Growth or Enterprise key can request the separate graph.
02
Choose a bounded direction
Use ancestors to follow corporate controllers above the subject. The default group direction also uses the daily PSC snapshot to discover bounded descendants and companies connected through shared corporate controllers.
03
Retain the coverage boundary
Read status, coverage, frontier, limits, and the snapshot alongside nodes and edges. A partial graph remains useful evidence, but it does not establish that no other ownership or control relationship exists.
Response surface
Fields to put in the workflow
The response uses named slabs, stable enum values, and null or empty values instead of silently omitting fields.
- nodes and edges
- Assessed UK companies and the Companies House PSC evidence connecting a controller to a controlled company. Node identity fields are name and status; edge identifiers remain available even when a controller cannot be resolved to a UK company number.
- snapshot and observed_at
- The pinned daily PSC snapshot used for discovery, plus separate Companies House and insolvency observation times for each node assessment.
- coverage and frontier
- Discovery and assessment completeness, assessed counts, and explicit reasons such as depth, node, edge, request, deadline, index, pagination, or identifier limits.
- related_risk.findings
- Contextual dissolved-company or insolvency findings for related nodes. They do not add points to, or become findings against, the subject company's main risk score.
Interpretation
A graph is bounded evidence, not an ownership verdict
Corporate PSC records describe control notified to Companies House. They do not guarantee exhaustive beneficial ownership, economic ownership, group membership, legal liability, or a complete path through foreign entities. Foreign and ambiguous identifiers remain unresolved rather than being joined by name or numeric resemblance.
Review prompts
- Which corporate PSC edges are supported by registry evidence?
- Was discovery and node assessment complete within the echoed limits?
- Which frontier entries require another source, a narrower follow-up, or human review?
- Are related-risk findings being kept separate from the subject company's own risk score?
First request
Start with a company number
curl "https://api.rotuli.co.uk/v1/entity/00445790/control-graph?direction=group" \
-H "Authorization: Bearer uk_live_YOUR_KEY"Control graphs require a Growth or Enterprise key. See the API reference for the full response schema and data sources for licence and freshness details.
Guide: trace and interpret a company control graph