If you've ever had to pull official company data for more than one country, you know the pain: every national business register is its own little world.
🇳🇴 Norway → Brønnøysund (BRREG) — great open API, Norwegian field names.
🇬🇧 UK → Companies House — REST, but its own auth and shapes.
🇩🇰 Denmark → CVR / Virk — where the CVR number is also the VAT number.
🇩🇪 Germany → Handelsregister — HRB numbers, registering courts, open data via OffeneRegister.
…and 30+ more, each different.
Integrating each one means a new endpoint, a new data model, new auth, new edge cases — and ongoing maintenance every time a register changes. For a KYC/KYB or onboarding flow that needs pan-European coverage, that's dozens of separate integrations before you've shipped a feature.
The "one schema" approach
The fix is to put a normalization layer in front of all of them, so every register returns the same JSON.…