CompliAPI changelog & release notes

Release notes for the CompliAPI sanctions screening API, MCP server, and dashboard — every new endpoint, improvement, fix, and breaking change, grouped by release period with a permalink per release. Breaking changes follow the versioning and deprecation policy.

Last updated · Subscribe via RSS · Longer-form notes on the blog

· Generated from 20 commits

No product-facing changes shipped this period — all commits this week were marketing site content, SEO copy, documentation, and internal pipeline tooling.

No entries in this period.

· Generated from 29 commits

CompliAPI adds real-time webhook notifications for sanctions list changes and upgrades search with regex mode and significantly faster fuzzy matching.

  1. NewWebhook notifications for sanctions list changes#

    Paid plans can now register monitored entities — crypto addresses, emails, websites, and government IDs — and receive signed webhook events the moment a watched value is listed, delisted, or relisted on a sanctions list. Automatic retry with exponential backoff and SSRF-safe endpoint validation mean your compliance workflows stay current without polling.

  2. NewRegex search mode for advanced sanctions lookups

    Both the API and the dashboard search now support case-insensitive POSIX regular expressions, letting you match complex name patterns, identifiers, or address formats in a single query. Wrap any query in forward slashes — /pattern/ — to activate regex mode; the same syntax works in the free SDN search tool.

  3. ImprovedFaster and more accurate fuzzy name matching

    Sanctions name searches are now up to 10× faster and return more relevant results: typo-tolerant word-similarity matching means a query like "ivanof" surfaces "Vladimir Ivanov", while list metadata like chain labels no longer crowd out entity matches. All searches also carry a per-request statement timeout to keep responses consistently fast under load.

  4. ImprovedMonitor entities directly from search results

    A new Monitor button on each search result and recently delisted row deep-links to the webhooks dashboard with the entity type, value, and label pre-filled — no manual copy-pasting required. Monitored-entity labels can also be edited inline without having to delete and re-add the entry.

  5. ImprovedDashboard typeahead is more responsive under load

    The search typeahead now cancels superseded in-flight requests so results always reflect your latest query, surfaces rate-limit information with a clear message instead of a generic error, and caches results within your session to reduce redundant requests.

· Generated from 25 commits

Self-serve account deletion, stronger password security, and expanded OFAC country data ship this week — plus new rate-limit headers and MCP resources for developers building compliance workflows.

  1. NewDelete your account directly from the dashboard

    You can now close your account from the Account settings page without contacting support — a short offboarding questionnaire and password confirmation are all it takes. Billing is cancelled automatically, and a confirmation email is sent when deletion is complete.

  2. NewRate-limit headers on every API response#

    All metered API responses now include standard RateLimit-Limit, RateLimit-Remaining, RateLimit-Reset, and RateLimit-Policy headers so your application can monitor quota consumption in real time and back off gracefully before hitting a 429. Monthly quota errors also include a Retry-After header pointing to your next reset.

  3. NewMCP server now exposes built-in compliance resources#

    The MCP server for AI agents now advertises two always-available resources — a live sanctions lists reference and a usage guide — so agent clients get useful compliance context without needing an authenticated session or burning API quota.

  4. NewOFAC sanctioned-country data refreshed and expanded#

    The OFAC country designations dataset now includes Afghanistan, Mali, Somalia, and South Sudan, and reflects Syria's transition from the comprehensive Syria program to the successor PAARSS program. Country data is also kept in sync automatically at startup and on a daily schedule, so production always reflects the latest designations without any manual intervention.

  5. NewPEP screening endpoint added to the project's payment activation flow#

    The /screen/pep endpoint is now included in the full suite of endpoints activated through the project's x402 payment layer, so developers can start screening for politically exposed persons in the same seamless flow as other compliance checks.

  6. ImprovedPassword strength indicator on signup and password reset

    A real-time strength indicator now guides you through meeting the project's password requirements — 12 or more characters with a mix of letters, numbers, and symbols — while creating or resetting your account. The same rules are enforced server-side, so you get clear, specific feedback rather than a generic error if a password doesn't qualify.

  7. ImprovedDocumented API versioning and deprecation policy#

    the project now publishes a formal API versioning policy: URL-based versioning, additive-only changes within a version, and a minimum 90-day notice window with Sunset and Deprecation headers before any breaking change. You can find the full policy in the API documentation.

· Generated from 15 commits

CompliAPI adds PEP screening and real-time rate limit visibility, while OFAC country designations now stay current automatically — giving compliance teams more coverage with less manual overhead.

  1. NewPEP Screening Now Available via API and MCP#

    You can now screen individuals against the global Politically Exposed Persons dataset using GET /screen/pep, with the same straightforward token-based access you use for OFAC sanctions checks. The endpoint is also available as a tool in the CompliAPI MCP server, so AI agents can run PEP checks alongside sanctions screening in a single workflow.

  2. NewRate Limit Headers on Every API Response#

    All metered CompliAPI responses now include standard RateLimit-Limit, RateLimit-Remaining, RateLimit-Reset, and RateLimit-Policy headers so you can monitor your quota in real time without logging into the dashboard. Monthly quota 429 responses also include a Retry-After header pointing to your next billing period reset.

  3. ImprovedOFAC Country Designations Stay Current Automatically#

    OFAC-sanctioned country data previously required a manual step after each deploy to take effect in production — that gap is now closed. CompliAPI syncs country designations automatically on startup and on a daily schedule, so your country-based screening always reflects the latest OFAC program coverage without any intervention.

  4. ImprovedUpdated OFAC Country Coverage: Afghanistan, Mali, Somalia, South Sudan, and Syria (PAARSS)#

    The curated OFAC country program data has been refreshed against the live OFAC program index as of August 22, 2026 — adding Afghanistan, Mali, Somalia, and South Sudan, and updating Syria to reflect the successor PAARSS program. CompliAPI's /screen/country endpoint now returns accurate designations across all 40 covered countries and territories.

  5. NewAPI Versioning and Deprecation Policy Now Published#

    CompliAPI now has a formal, documented versioning and deprecation policy: URL-versioned endpoints, additive-only changes within a version, and a guaranteed 90-day notice period with Sunset and Deprecation headers before any breaking change takes effect. You can plan integrations with confidence knowing exactly how and when the API will evolve.

  6. ImprovedMCP Server Resources Now Advertise Available Sanctions Lists and Usage Guide#

    The CompliAPI MCP server now exposes two built-in resources — a sanctions lists reference and a usage guide — so AI agent clients receive a populated resources list immediately without needing an authenticated session. This improves out-of-the-box discoverability for teams integrating CompliAPI into agentic compliance workflows.

Powered by Shipstar