Introduction

Legal notice

Information provided by iGregulator is sourced from public regulator records and is intended for informational purposes only. License verification results do not constitute legal advice. Customers are responsible for their own compliance, KYB, and AML decisions. Always confirm critical licensing decisions directly with the issuing regulator. Full terms at /terms.

iGregulator is a REST API for verifying iGaming operator licences against the public registers of six regulators — UK Gambling Commission (UKGC), Malta Gaming Authority (MGA), Curaçao Gaming Authority (CGA, post-LOK), Kahnawake Gaming Commission (KGC), Anjouan Gaming Authority (AGA), and Tobique Gaming Commission (TGC). Daily-refreshed; updated within 24 hours of regulator changes.

Building with AI? → /docs/for-ai-agents covers MCP, structured errors, _meta provenance, and machine-readable resources (llms.txt, OpenAPI) for LLM integrations.

What you can do with it

• Verify a domain — hit GET /v1/check?domain=X and get an operator + licence + confidence score in one round-trip.
• Look up an operator — search by name or trading name via GET /v1/operators/search?q=… and drill into licences, domain portfolios, and regulatory actions.
• Pull a whole jurisdiction — paginate GET /v1/jurisdictions/:code/operators for a clean dataset of everyone currently licensed.
• Track regulatory actions — enforcement decisions (fines, warnings, licence revocations) surface via the operator detail endpoint.

Data coverage (live as of April 2026)

Jurisdiction	Licences	Source	Cadence
UKGC	~3,460	Public register ZIP	Daily 03:00 UTC
MGA	~310	Playwright-scraped SPA	Daily 03:15 UTC
CGA	~650	OGL PDF parse	Daily 03:30 UTC
KGC	~60	Interactive Gaming + CSPA HTML	Daily 03:45 UTC
AGA	~1,275	Embedded JSON on register page	Daily 04:00 UTC
TGC	~160	Static HTML table (via CF Worker proxy)	Daily 04:15 UTC

Who it’s for

Four buyer profiles drive the product today:

• Affiliate sites — verify that a brand they’re promoting is still licensed before writing reviews and paying out referral payments.
• Compliance + AML teams — weekly sweeps of their operator counterparties for status changes and enforcement actions.
• Payment providers — merchant onboarding checks + ongoing KYB.
• Investment intelligence — correlate licence churn, enforcement fines, and domain-expiry signals into early-warning scores.

Start here

1. Getting started — first curl call in under a minute.
2. Authentication — when you graduate from the public 10 req/hr limit.
3. Confidence scoring — how the /v1/check endpoint picks between high, medium, and low.
4. API playground — try any endpoint interactively.
5. Full endpoint reference — detailed schemas for every route.