UFLPA Entity List Monitor & Delta Tracker

The authoritative DHS UFLPA Entity List — the U.S. government's list of companies whose goods are barred from import under the Uyghur Forced Labor Prevention Act's rebuttable presumption of forced labor — as clean, structured, screenable data, plus delta tracking of every addition over time.

If you import into the United States, screening counterparties against the UFLPA Entity List is not optional: U.S. Customs and Border Protection detains merchandise linked to a listed entity at the port, on issuance. This actor turns the list DHS publishes as three HTML tables into one row per entity — with aliases, effective dates, the statutory sub-list, and the originating Federal Register notice — so you can screen it, diff it, and wire it into a compliance pipeline.

Most trade-compliance tools on the market slap a derived "forced-labor risk" flag onto third-party shipping data. This is the actual list, reproduced faithfully from the primary source, and tracked for changes.

Who it's for

• Importers & customs brokers — screen suppliers and their upstream vendors before a shipment is detained.
• Trade-compliance & sanctions teams — keep an internal screening list current; get alerted the day new entities are added.
• Supply-chain / ESG / forced-labor due-diligence — map exposure to Xinjiang-linked entities and the "poverty alleviation" / "pairing-assistance" labor programs.
• Procurement & vendor onboarding — check a new counterparty (and its aliases) against the ban list in one call.
• Freight forwarders, 3PLs, sourcing agents — verify goods will clear before they move.
• AI agents — a clean, chainable UFLPA-screening tool (see "Use as an MCP tool").

What it does

• Reads the primary source. The current list comes straight from the DHS UFLPA Entity List page (dhs.gov/uflpa-entity-list), organized by the four statutory sub-lists under UFLPA Section 2(d)(2)(B).
• Parses aliases faithfully. A company hiding under an alias, a.k.a., or former name is still caught — search matches names and aliases (e.g. "Bingtuan" resolves to the Xinjiang Production and Construction Corps).
• Attributes each entry to its Federal Register notice by effective date, so you can cite the source of every addition.
• Cross-checks currency. Every run corroborates the DHS page against the newest UFLPA Entity List Federal Register notice, so you know the list you got reflects the latest official update.
• Tracks changes. delta mode reports only what is new since your last run — the additions that matter for an alerting pipeline.

Modes

list — the full current list (default)

Returns every entity-by-sub-list row on the current UFLPA Entity List (about 200 rows today; it only grows).

{ "mode": "list", "maxResults": 500 }

search — screen a counterparty

Filter by company name (matched against names and aliases) and/or a statutory sub-list.

{ "mode": "search", "query": "Hoshine" }

{ "mode": "search", "sublist": "v" }

delta — new since last run

Reports entries added since your previous run for the same scope, using a named cross-run baseline. The first run for a scope stores a baseline and fails with an explanatory message (rather than billing the whole list as "new") — schedule it and subsequent runs report genuine additions.

{ "mode": "delta" }

Optional date window (any mode)

addedSince / addedUntil filter by the entry's effective (added) date. Strictly YYYY-MM-DD — slash dates and month names are rejected loudly rather than applied ambiguously.

{ "mode": "list", "addedSince": "2025-01-01" }

Output fields

One row per entity × statutory sub-list (an entity on two sub-lists yields two rows; entity_appears_on_sublists names them all).

Field	Meaning
entity_name	Canonical company/facility name
entity_name_full	Full name exactly as DHS lists it (with the alias parenthetical)
aliases / alias_count	Published aliases / a.k.a. / former names (|-joined) — screen against these too
sublist / sublist_section / sublist_label	Which UFLPA §2(d)(2)(B) sub-list and its statutory basis
effective_date_iso / effective_date_raw	When the entity was added on this sub-list
entity_appears_on_sublists / entity_sublist_count / is_multi_sublist_entity	Full sub-list membership for the entity
entity_first_effective_date_iso	When the entity was first added to the list
source_fr_document_number / source_fr_url	Originating Federal Register notice (matched by effective date)
is_new_since_last_run / delta_baseline_status	delta mode: additions since last run (null in other modes — "not checked", never a guessed false)
latest_fr_notice_*	The most recent UFLPA Entity List FR notice (document number, date, URL)
dhs_current_with_latest_fr_notice	Whether the DHS page reflects that latest notice
drift_gate_status	verified or verified_degraded (a corroborating check was unavailable — disclosed, not hidden)
list_total_occurrences / list_total_unique_entities	Size of the current list this run parsed
matched_total / results_truncated / run_max_results_cap / rows_emitted_this_run	So a capped answer is never mistaken for a complete one
occurrence_key	Stable identity (normalized name :: sub-list) — the delta identity

Scope and cost — read this first

• Pricing: pay-per-result at $12 per 1,000 rows (with graduated volume discounts on paid tiers).
• The entire current list is only ~200 rows, so a full list pull costs roughly $2.40. A search for one company costs a few cents. A delta run bills only the genuinely new entries — usually $0 on a run where nothing was added.
• maxResults is a hard cap on rows emitted and billed. Every row carries matched_total and results_truncated so you always know whether you got the whole answer.
• If the source cannot be reached and verified, the run fails and bills nothing. A UFLPA screen must never report "clear" from an unreachable list — so you are never charged for a run that could not actually confirm the list.

Correctness — why you can trust a "clear"

This actor is built so that an empty or "not found" answer is only ever produced when it is genuinely true:

• Live drift gate before any billable row. Every run verifies (1) the list is at least a floor size, (2) a pinned long-standing entity (the Xinjiang Production and Construction Corps) is present on its expected sub-list and effective date, (3) a nonsense query matches nothing, and (4) the DHS page reflects the latest Federal Register notice. If the load-bearing checks can't complete, the run fails loudly — it does not emit a clean empty list.
• HTML-error-page guard. A maintenance or rate-limit page served at HTTP 200 is rejected, never parsed into an empty "no entities" answer.
• Aliases are first-class. A counterparty on the list under an alias is matched — the failure mode of "screened clear because we only checked the primary name" is designed out.
• Faithful, not derived. Names, sub-lists, effective dates and aliases are reproduced from the primary source; nothing is inferred or scored.

Use as an MCP tool

This actor is callable by AI agents (Claude, Cursor, etc.) via Apify's MCP server (mcp.apify.com). Its input and output fields are fully described, so an agent can screen a counterparty and chain the result into a decision.

Worked agent prompt:

"Screen the supplier Hesheng Silicon Industry against the UFLPA Entity List. If it appears (including under any alias), tell me the statutory sub-list, the effective date, and the Federal Register notice."

Billing is unchanged when called as a tool: you pay per result row, and a run that cannot verify the list fails without billing.

FAQ

Is the UFLPA Entity List free to check somewhere? DHS publishes it as HTML tables you must read by eye. This actor turns it into structured, searchable, diff-able rows with aliases and source citations — the work of screening and monitoring, not just reading.

How current is it? It reads the live DHS page every run and corroborates against the newest UFLPA Entity List Federal Register notice. dhs_current_with_latest_fr_notice tells you whether the page has caught up to the latest notice.

What are the sub-lists (i)/(ii)/(iv)/(v)? The statutory categories under UFLPA §2(d)(2)(B): (i) Xinjiang entities that mine/produce/manufacture with forced labor; (ii) entities working with the Xinjiang government to source forced labor; (iv) exporters into the US; (v) entities/facilities sourcing material from Xinjiang or from government forced-labor programs. (iii)/(iv) currently carry no separate DHS table — DHS states no additional exporters have been identified.

Does it include addresses? DHS does not publish addresses on the Entity List — only entity names, aliases, and effective dates — so this actor does not fabricate them. It provides the name, aliases, sub-list, effective date, and source notice.

Does the row count match DHS's headline number exactly? This actor reports its own measured totals (list_total_occurrences, list_total_unique_entities). DHS's headline count can differ slightly from the unique-name count because of how multi-sub-list and descriptor variants are counted; the list content is reproduced faithfully either way.

Source & disclaimer

Data: U.S. Department of Homeland Security UFLPA Entity List (dhs.gov/uflpa-entity-list) and the Federal Register API (federalregister.gov), both public and keyless. This actor is an unofficial convenience tool and is not affiliated with DHS, CBP, or the Forced Labor Enforcement Task Force. Always confirm a screening decision against the official DHS list and the relevant Federal Register notice; this actor cites both on every row.