US Tariff Revision Diff & HTS Change Monitor (Unofficial)

Compare two official USITC HTS releases and get only the tariff lines that changed, with old/new field evidence and source revision metadata.

Use it when you already know the HTS codes you care about and need to answer:

• Did any watched code change between two releases?
• Which descriptions, units or published duty-rate fields changed?
• Was a code added or removed?
• What is the current official release identity?

Modes

Mode	What it does	Typical cost
revisions	Official release list (name, status, dates)	start fee only
current	Normalized current-release records (filter by codePrefixes)	per emitted record
diff	Changes between a previous snapshot and the current release	per changed record
watchlist	Same as diff, filtered to your exact codes	per changed record

Snapshot workflow (recommended)

1. Run mode=current (optionally with your codePrefixes) and note the dataset ID.
2. When a new USITC revision is published (check mode=revisions), run mode=diff with fromDatasetId = that dataset ID.
3. Store the new snapshot for next time.

Every diff output record includes the HTS key, change type (added / removed / modified), the changed fields with exact old/new values, and a meta record with the target release name and the raw SHA256 of the official source payload.

Example input

{
  "mode": "diff",
  "fromDatasetId": "your-previous-snapshot-dataset",
  "codePrefixes": ["72", "73"],
  "maxChanges": 500
}

Example output record

Real observed change — 2026HTSRev14 → 2026HTSRev15 (official USITC archive):

{
  "key": "99030463",
  "changeType": "modified",
  "changedFields": [
    { "path": "$.general", "old": "The duty provided in the applicable subheading + 10%",
      "new": "The duty provided in the applicable subheading +0%", "kind": "value_changed" },
    { "path": "$.special", "old": "The duty provided in the applicable subheading + 10%",
      "new": "The duty provided in the applicable subheading +0%", "kind": "value_changed" }
  ]
}

That transition produced exactly 2 semantic changes (99030306 description edit + 99030463 rate cut to +0%). A large revision looks like this — 2026HTSRev1 → 2026HTSRev2: 295 records changed (176 added, 66 removed, 53 modified).

Mass cross-cutting note changes are grouped into events instead of thousands of noisy records (observed: 2026HTSRev12 → 2026HTSRev13, 10,502 footnote rows collapsed into 13 events + 939 semantic changes; 101 new 9903.88.x lines added).

Spending protection

The Actor always respects your run's max-cost limit:

• Set maxTotalChargeUsd in the run configuration (Apify enforces it too).
• The Actor stops charging and stops emitting billable records the moment the next event would exceed the limit, then returns a meta record with chargedUsd, limitUsd and limitReached.
• You never pay for output beyond your limit, and runs end cleanly instead of being aborted mid-stream.

Source and legality

• Data source: official USITC HTS portal — https://hts.usitc.gov (public government data, no auth) and the official HTS archive — https://www.usitc.gov/harmonized_tariff_information/hts/archive (CSV/XLS/JSON historical releases).
• This Actor is not a customs classification service and does not provide legal advice.
• Always verify decisions against current official USITC/CBP guidance.
• No LLM is used in the data path; every fact is a deterministic transformation of the official payload.