OpenKrill's Tariff & HS Code Duty Finder is a no-key MCP server that finds candidate HS and HTS codes and reads the printed duty for the UK and US. It excludes US Chapter 99 duties such as Section 301 and 232. Tariffs API returns the full stacked US rate by origin and date, with sources. Compared 31 Oct 2026.
Source: USITC HTS 2026HTSRev22 · Synced
Card required · cancel anytime in 14 days
Tariffs API vs OpenKrill's Tariff & HS Code Duty Finder.
OpenKrill gives an AI assistant candidate codes and the printed duty for the UK and US, with no key. It leaves out US Chapter 99, which is where Section 301 and 232 live.
OpenKrill's Tariff & HS Code Duty Finder is a remote MCP server with two tools: one suggests candidate codes from a plain description, the other reads the duty for a code in the UK or US tariff. For the UK it adds VAT and preferential rates. For the US it returns the general, special and column 2 rates, and in its own words, Chapter 99 additional duties are not included. If the US number you need includes Section 301 or 232, that gap is what this page is about.
Tariffs API vs OpenKrill
| Feature | Tariffs API | OpenKrill |
|---|---|---|
| What it returns | The effective US rate for an HTS code from a given origin on a given date, with each Chapter 99 measure | Candidate codes from a description, and the duty printed for a code: US general, special and column 2 rates; UK third-country duty, VAT and preferential rate Source, checked |
| US Chapter 99 (Section 301, 232, 338) | Included, resolved by origin and date | Not included Source, checked |
| Per OpenKrill's integration page (accessed 2026-10-31): "Chapter 99 additional duties for the US and quotas or trade remedies are not included." | ||
| Origin-aware US stacking | Origin is a parameter; every applicable measure is stacked on the base duty | Optional origin, but with no Chapter 99 duties there is nothing to stack Source, checked |
| Per OpenKrill's importer page (accessed 2026-10-31): "US chapter 99 additional duties are not included." | ||
| Countries covered | US imports | UK and US imports; not the EU TARIC list Source, checked |
| Codes from a product description | No. We report rates on codes you already have | Yes, labelled as candidates, not binding classification Source, checked |
| Interface | REST + JSON API; MCP server on the Developer plan | Remote MCP server over Streamable HTTP; a REST API is not stated Source, checked |
| Authentication | API key, self-serve signup | No API key Source, checked |
| Limits | Monthly call quota by plan | 60 tool calls a minute from one network; 25,000 a day per server, shared by all callers Source, checked |
| Per OpenKrill's integration page (accessed 2026-10-31): higher limits by emailing them for a key, and "There is no SLA yet." | ||
| Price | Public pricing, self-serve: see /pricing; 14-day trial | Not stated on its public pages |
| Historical dates | as_of parameter resolves the rate in force on that date | Not stated on its public pages |
| Freshness | USITC releases polled every 6 hours | Answers cached for up to 6 hours Source, checked |
Claims about OpenKrill as checked on their public pages, linked per row where a page states it and listed under Sources. Want to see a number first? Try any code in the tariff calculator, no signup.
When OpenKrill is the right pick
- →You want a tariff tool inside an AI assistant with no API key to manage.
- →You import into the UK and need the third-country duty, VAT and preferential rate.
- →You need candidate codes from a product description. We don't classify products.
- →The printed US rate is enough, because none of your goods carry Chapter 99 duties.
When Tariffs API is the right pick
- ✓Your US number has to include Section 301, 232 or 338, stacked by origin.
- ✓You need the rate in force on a specific date, for an invoice or an audit.
- ✓You're calling from your own code over REST, with a key and a quota you control.
- ✓You already have the HTS code and need the duty, not a candidate list.
One endpoint. Deterministic JSON.
Send an HTS code, an origin and an optional as_of date to GET /api/v1/tariffs/resolve. The response carries the base duty and every applicable Chapter 99 measure with its heading, stacked into one total, with source links to USITC and the Federal Register.
GET /api/v1/tariffs/resolve?hts=8541.10.00.80&origin=CN&as_of=YYYY-MM-DD&resolve_chapter_99=true
{
"summary": {
"applicable_ad_valorem_rate": <percent: base + direct ad valorem measures>,
"resolved_additional_ad_valorem_rate": <percent: Chapter 99 total>,
"total_resolved_ad_valorem_rate": <percent: base + additional>
},
"base_tariff": { "percentage_component": <fraction> },
"additional_measures": [
{
"program": "section_301",
"chapter_99_code": "9903.xx.xx",
"percentage_component": <fraction>
}
]
}Switching from OpenKrill
Does OpenKrill include Section 301 and Section 232 duties?
No. OpenKrill's own pages say Chapter 99 additional duties for the US, and quotas or trade remedies, are not included. Section 301 and 232 are Chapter 99 measures, so the US rate it returns is the printed base duty only. Tariffs API resolves those measures by origin and date and stacks them on the base.
Can I use OpenKrill and Tariffs API together?
Yes. OpenKrill suggests candidate codes from a description, which we don't do. Once you or your broker have confirmed the code, Tariffs API returns the full US rate for it from a given origin. Candidate codes are not binding classification, on either side.
Does Tariffs API cover UK duty and VAT?
No. We cover US imports. OpenKrill reads the UK tariff, including VAT and the preferential rate for an origin, so for UK imports it answers a question we don't.
- OpenKrill: Tariff & HS Code Duty Finder in VS Code · accessed
- OpenKrill: tools for importers · accessed