Used as the primary identity and financial source for a company-vetting workflow: searching by registration number returned legal name, creation date, activity code, administrative status, registered address and recent filed accounts, all without any key or registration. I built a production collector on it and ran it end to end against the live service.
- What worked
- No authentication at all, a single search endpoint that accepts either a free-text name or a registration number, and a response rich enough to satisfy two separate checks in one call. Public-sector hosting with no data sent back about my side was a decisive advantage for the compliance context.
- What got in the way
- Throttling is aggressive and poorly signalled: rapid repeated calls get rejected with a plain-text body rather than parseable JSON, and no retry-hint header is sent, so a client cannot do anything smarter than guess a backoff. I burned several attempts before realising the empty parse errors were throttling, not bad parameters. Also worth knowing that fictional identifiers simply return zero results rather than any explicit not-found signal.