ig iGregulator
~/about

About iGregulator

Mission

iGregulator turns the world's iGaming licensing registers into a single machine-readable API. We scrape regulator websites daily, normalise the records into a consistent schema, and surface the result through a REST API and an MCP server so compliance teams, payment providers, and affiliate networks can verify operator licenses programmatically instead of clicking through PDF dumps.

Founder

Anatolii Ohorodnyk — EU-based, DevOps and infrastructure background. iGregulator started as a personal scraper for a side project that needed to know which Curaçao operators had survived the post-LOK transition; it kept finding edge cases the existing compliance suites either missed or charged enterprise contracts to expose.

Solo-built. Self-funded. No outside investors, no marketing team, no sales pipeline — every minute spent on the product goes into the scrapers, the API, and the docs you're reading.

Why we built it

The compliance-tooling market has two tiers. At the top: enterprise suites (Vixio, Gambling Compliance, ComplianceOnline) built around annual enterprise contracts and lawyer review. At the bottom: free manual research — opening the UKGC public register in one tab, the MGA register in another, and copy-pasting into a spreadsheet.

The middle is empty. There's nothing developer-grade — REST API, OpenAPI spec, webhooks, MCP server — that a compliance engineer at a payment provider, an affiliate network, or a fast-moving startup can wire up in an afternoon and price against actual usage.

That's the gap iGregulator fills. Keyless lookups and every public page are free; Starter is €45 a month with the first 14 days free (card required), and Pro and Business are paid by card or by invoice. How we verify — sources, provenance, corrections — is in our methodology; every register is read daily, and every status shows when we last read it — live per-register freshness is on the status page.

Coverage

Fourteen jurisdictions live today (live counts per register: /v1/stats):

See coverage methodology for how we compute domain coverage per regulator and which license types we consider in scope.

Contact

Read next