You give it up to three HTS codes. When an official USITC revision changes one of them, it tells you the old value, the new value, and the official citation it read that from.
https://hts.usitc.gov. Non-official hosts, non-JSON responses and malformed payloads are refused, never guessed at.review_required and no change — it does not guess.It does not classify goods, and it is not customs or legal advice. You supply the codes; it only watches them.
Up to three watched HTS codes. US scope.
The single paid plan. No checkout is wired up in this MVP — nothing here takes a payment.
Every endpoint is a plain GET returning JSON. No key, no account, no tracking.
| Endpoint | Returns |
|---|---|
api/index.json | Service index |
api/health.json | Liveness |
api/plan.json | Free tier and the one paid plan |
api/disclaimer.json | The standing disclaimer |
api/revisions/index.json | Accepted revisions with checksums |
api/reports/changes-detected.json | A worked change report |
api/reports/review-required.json | A worked ambiguity refusal |
curl -s https://danielarif26.github.io/tariff-revision-impact-feed/api/reports/changes-detected.json
The reports published here are produced by running the service's own comparison code over recorded USITC-shaped revision fixtures, so the behaviour you read is the behaviour the code actually has. They are worked examples of the format, not a live feed of today's tariffs.