About Stratum APIs

Public data in the UK is, on paper, free. In practice each source has its own quirks: a regulator's register paginated differently from its own affiliated lookups; a government CSV with metadata in row 0; an XML feed that uses self-closing elements and breaks naive parsers; an upstream that quietly migrates to a new domain and decommissions the old one a year later.

Stratum takes those sources, normalises them, joins them where useful, and serves the result as boring, predictable JSON. You write the integration once, against our contract, rather than against six government portals.

Our APIs are grouped into clusters, each anchored on a real-world domain where multiple data sources cross-reference each other:

• Compliance: regulator registers, sanctions lists, corporate filings, AML / KYB enrichment.
• Property: energy performance certificates, postcode geography, planning, tenure.
• Business intelligence: corporate health, director track records, official notices.
• Vehicle: DVLA, MOT history, recall checks.
• Connectivity: broadband and mobile coverage, cell tower data, fixed-line availability.

We launch within a cluster when there's clear buyer demand and a public source we can stand behind. New clusters get added when the same is true for a new domain: healthcare professionals, education, environmental data, infrastructure. Suggestions welcome via the contact page.

31M+ UK records under live monitoring across 6 datasets, served through an active catalogue of APIs. The full, up-to-date list, including pricing, response shape, refresh cadence and example calls, lives at /apis.

Compliance was our first cluster because it's where we got asked the most early. Other clusters are in active build; the cadence is roughly one new API every few weeks.

UK-hosted on AWS in eu-west-2 (London), fronted by Cloudflare. Each API is its own Lambda behind a shared API Gateway and a single developer-facing key. Datasets that we host ourselves are refreshed on EventBridge schedules (daily for fast-moving sources, monthly for slow ones); datasets we proxy are queried live with short-TTL caching.

Auth is handled by Clerk, billing by Stripe. We hold the bare minimum of personal data required to operate the service; see the privacy policy for the full breakdown.

Most teams that need UK public data end up building the same scrapers and parsers, then maintaining them when the upstream moves. We'd rather solve that once, well, and sell the result cheaply, and we'd rather show our pricing on the page than make you schedule a demo to find out. Both choices are deliberate, and they shape what we build next.

Sales, support, partnerships and dataset suggestions all welcome: contact page.