Market validation

Sanctions Compliance Change Monitor

A proposed public-data API and feed for teams that need OFAC sanctions list changes, entity lookups, and watchlist deltas in automation-friendly JSON or spreadsheet-ready CSV.

Request this feed View current demo Open paid API

GET /v1/sanctions/changes?list=ofac&since=2026-07-01&entity_type=entity

{
  "data": [
    {
      "listName": "OFAC SDN",
      "entityName": "Sample Shipping LLC",
      "entityType": "entity",
      "program": "SAMPLE-PROGRAM",
      "changeType": "added",
      "observedAt": "2026-07-02T15:20:00Z",
      "source": "OFAC SLS"
    }
  ],
  "meta": { "sampleOnly": true, "market": "sanctions-compliance" }
}

Validation Thesis

This concept is only built further if tracked requests, demo clicks, or marketplace intent justify the build.

OFAC and sanctions list change monitoring for compliance operations.
Watchlist CSV exports for teams that start with spreadsheet review.
API demand from fintech, marketplace, supplier, and KYB workflows.

Public Data Sources

The initial product would normalize public records into stable polling endpoints and exports.

OFAC Sanctions List Service
OFAC SDN List and Non-SDN Consolidated Sanctions List
OFAC archived published delta files

Buyer Workflows

These are the specific self-serve workflows this page is testing before any backend is built.

OFAC list delta feed

Poll for additions, removals, and updates across OFAC SDN and non-SDN list files without hand-checking data downloads.

Counterparty watchlist review

Export public list changes to compliance review queues for vendors, customers, vessels, and companies.

Screening integration input

Normalize list, program, entity type, alias, and source fields for products that already own final match decisions.

Specific Workflow Tests

These pages test sharper buyer searches before implementation.

Workflow validation OFAC Sanctions Watchlist API OFAC sanctions list deltas for compliance automation

Monetization Hypothesis

Pricing only becomes meaningful after tracked demand appears. The first offer should stay narrow and low-touch.

Validation-first CSV feed before direct payment links or KYC onboarding
Paid API tier only if sanctions request clicks or sample downloads appear
Higher tiers would require clear disclaimers and acceptable-use boundaries

Validation FAQ

Is this a live sanctions screening product?

No. This is a validation page. It tests demand for public sanctions list change data before building an API or CSV feed.

Would it make compliance or legal decisions?

No. The proposed product would provide public-source data and source links only. Buyers remain responsible for their own screening, matching, and compliance decisions.