Duty straight off the official schedule, with the revision attached

Because the code is not declarable. A measured lookup of UK heading 6403 returned declarable false with import_duty null, vat null and a note saying rates are published at the declarable level — plus context[] with 60 child lines to choose from. That is the answer, not a failure: a 4-digit heading is a category, and duty is set per specific line. Walk into context[] and pick the child that matches the goods, then look that up. Do not assume that adding zeros to a heading produces a valid line.

No. Measured, UK 6109100000 for T-shirts came back declarable false with null rates, while 6403120000 with the same digit count came back declarable true with an 8.0% duty. Declarability is a property of the tariff line in the schedule, not of its length, because some ten-digit codes are themselves intermediate nodes. Always branch on the declarable boolean and never on len(code).

Treat it as a shortlist, never as an answer. It is a relevance heuristic over the tariff text — the response says so in confidence_note — and the score reflects search rank, not correctness. A measured UK classification of 'leather shoes for men, leather upper' returned a top candidate at confidence 0.95 with confidence_band 'high' and review_required false, and that candidate was a sports-footwear line: tennis shoes, basketball shoes, gym shoes. High confidence there means a strong text match, not the right code. Use it to narrow to a chapter, then confirm the line with hs_lookup and a broker.

Transparently, and the assumptions travel with the answer. A measured UK estimate on a 1,200 value with 80 shipping and an 8.0% duty line returned estimated_duty 96.0 — eight percent of the customs value alone, not of value plus shipping — with VAT computed on value plus shipping plus duty, and total_landed_cost 1,376.0 in a breakdown you can check by hand. Read assumptions[] every time: it states that the general third-country MFN rate was applied for the origin you gave, that trade-preference (FTA) rates, anti-dumping duty and US Section 301/232 surcharges are NOT applied automatically, and that no currency conversion happens — all figures stay in whatever unit you passed.

How many preferential rate measures exist on that line, as a count — 56 on the measured ski-boot code. It is a signal, not a rate: it tells you there is real money to be found if your goods qualify under an FTA, a GSP scheme or a quota, and that the MFN figure you were quoted is the worst case. It does not tell you which ones you qualify for, and we do not guess at that; origin rules are the part that needs a human.

It means the government schedule itself did not answer. Observed against the US side: hs_lookup returned UPSTREAM_HTTP with 'no HTS data for heading 8471 (status 503)' and retryable true, while landed_cost on the same code returned the same underlying failure with retryable false. The difference is deliberate — a lookup is worth retrying because the .gov service may recover in seconds, but a landed-cost estimate has no meaning without a tariff line, so retrying the whole calculation is wasted work. Fix the lookup first, then recompute. During an outage classify can also return zero candidates for that market, which is an empty index rather than an unclassifiable product.

No, and every response says so. The data is pulled from the official published schedules — USITC HTS for the US and HMRC's live Trade Tariff for the UK, both named in source and pinned by schedule_version — but a classification is only binding when the customs authority issues it. Each declarable UK line carries a bti_url pointing at the binding-decision process. Use this to estimate, to compare markets and to check a broker's work; do not use it as the sole basis for an entry.

The full path above your code, which is what you need to explain a classification to somebody. A measured ski-boot lookup returned section XII with its full title, chapter 64 'Footwear, gaiters and the like; parts of such articles', and heading 6403 'Footwear with outer soles of rubber, plastics, leather or composition leather and uppers of leather'. Sections are Roman numerals and chapters are two digits, which is worth knowing before you try to sort them as integers. Alongside it, validity_start and validity_end date the line — a null validity_end means the line is currently in force.

HS Code & Tariff API is a ReefAPI endpoint group for hs code & tariff It returns live JSON through POST requests under /hs-code/v1.

Yes. ReefAPI starts with 1,000 free credits, no card required. HS Code & Tariff calls use the same shared credit balance as every other ReefAPI engine.

No login to HS Code & Tariff is needed for the API response. You call ReefAPI with your x-api-key header, and the playground can run live examples before you create a production key.

The page example is captured from a live hs_lookup call, and production requests fetch live data through ReefAPI rather than a static sample.

HS Code & Tariff actions currently cost 1-8 credits per successful call. Failed or blocked calls are free, and all APIs draw from one credit pool.

Yes. Connect ReefAPI once through MCP and your assistant can call hs-code actions with the same key, credit pool and JSON envelope used by normal REST requests.