A clean machine-readable database of obligations, penalties, scope, and regulator citations across global compliance — designed for compliance products, fintech engineers, and the AI agents being shipped right now.
# Fetch GDPR-tagged privacy regulations curl "https://api.regintelapi.com/regulations?jurisdiction=EU&category=Privacy" \ -H "x-api-key: YOUR_API_KEY" # Response — structured, cited, machine-readable { "data": [{ "id": 123, "jurisdiction": "EU", "category": "Privacy", "short_title": "GDPR 2016/679", "obligations": "Lawful basis required...", "penalties": "Up to €20M or 4% global turnover", "source_url": "https://eur-lex.europa.eu/...", "uri": "https://api.regintelapi.com/regulations/123" }], "meta": { "total": 212, "credits_used": 1 } }
Six capabilities, no surprises. Every record traces back to the regulator's own publication.
Obligations, penalties, scope, key articles, tags — all broken out as clean JSON. No PDF parsing, no manual extraction.
Every regulation includes a source_url pointing to the upstream regulator. Citation-ready out of the box for LLM grounding.
Each record has a stable uri identifier. Use as a vector-store key, agent memory token, or cite-this anchor.
The /updates endpoint returns what's new and amended in any window. Drives incremental cache sync.
Both x-api-key and Authorization: Bearer accepted. Same token. Standard OAuth-style or simple header.
Ship a working tool to Claude Desktop in 60 seconds. pip install regintel-mcp and paste the config block.
RegIntel powers the regulatory layer underneath compliance tools that used to take ten people to build.
Feed cited regulatory context directly into LLM prompts. The structured fields ground the model; the source URLs let it cite the regulator.
Embed cross-border regulatory checks into onboarding, payment, and KYC flows — without standing up a compliance team to maintain rules.
Build monitoring, audit, and regulatory-change tracking on top of an API that's always current and always cited.
Seven customer-facing endpoints. Filterable by jurisdiction, category, tag, and date range.
{
"data": {
"id": 123,
"uri": "https://api.regintelapi.com/regulations/123",
"jurisdiction": "EU",
"category": "Privacy",
"short_title": "GDPR 2016/679",
"obligations": "Establish a lawful basis under Article 6 before processing...",
"penalties": "Up to €20M or 4% of global turnover",
"source_url": "https://eur-lex.europa.eu/eli/reg/2016/679/oj",
"status": "active"
},
"meta": { "credits_used": 1 }
}
1 credit = 1 successful billed API call. /jurisdictions is free. Upgrade or downgrade any time.
Need more? Contact us for enterprise pricing →
Quick answers about RegIntel.
RegIntel is a structured regulatory database covering 41 jurisdictions and 212+ regulations, with obligations, penalties, scope, and regulator citations exposed as both a REST API and an MCP server. It's designed for compliance products, fintech apps, and AI/RAG pipelines that need clean, machine-readable regulatory data with cited sources.
41 jurisdictions today, including the EU (GDPR, MiCA, DORA), United States (SEC, FINRA, CFTC), Australia (APRA, ASIC), Singapore (MAS), United Kingdom (FCA), and many more. New jurisdictions are added regularly via a Claude-assisted weekly research loop, with human review before publishing.
No. The Free plan gives you 100 credits with no time limit and no credit card. You only add payment details when you upgrade to a paid plan.
Standard REST API, key-based auth, JSON responses. Most developers integrate the first endpoint in under 10 minutes. Code examples in Python, JavaScript, and curl are in the docs. If you want it as a Claude Desktop tool, pip install regintel-mcp and paste the config block in our MCP repo README.
No. RegIntel provides structured regulatory intelligence, not legal counsel. The data is sourced from official regulator publications and cited accordingly, but compliance decisions should be validated with qualified counsel for your specific facts.