htsapi.dev

How classification is done, and why we give sources

This is the method professionals follow, drawn from CBP's own guidance (the informed compliance publications Tariff Classification and Reasonable Care) and USITC's advice. Our MCP server's instructions walk an agent through it, and each step names the tool that serves it.

The method

  1. Facts first. What the product is, what it is made of (with percentages), how it works, what it is for, and how it is imported (set, kit, unassembled, packaging, cost of each part). Missing facts are the commonest cause of a wrong code: ask for them rather than guess.
  2. The heading, by GRI 1. The four-digit heading is decided by the terms of the headings and the section and chapter notes, not by titles or keywords. A ceramic paring knife looks like heading 8211, but chapter 82's notes send it to chapter 69. Tools: search_rulings to see how CBP classified similar goods (a candidate, not an answer); lookup_hts_code to read the schedule; get_notes for the notes; heading_scope for what CBP's rulings say each candidate heading covers.
  3. Only if several headings still fit: GRIs 2 to 5. Unfinished goods and mixtures, the most specific description, essential character (by material, bulk, weight, value or role), last in numerical order.
  4. Down the tree, by GRI 6. Compare subheadings only at the same level, one level at a time, with lookup_hts_code. An "Other" line says what the goods are not.
  5. Check before relying on a code. rulings_under_code shows every ruling under a code and the rulings CBP revoked off it, with where it moved the goods. get_ruling gives a ruling's full text and its status: only a current ruling is authority, and a ruling binds only its own goods.
  6. If it stays unclear, the importer can ask CBP for a binding ruling (19 CFR part 177).
  7. Keep the file: the facts, the headings considered, the notes and GRIs applied, the rulings relied on and any against, the code, the date. The MCP prompt classification_file sets it out.

What each source holds, and its limits, is on What's inside. How to connect is on Connect.

Why we give sources, not a code

CBP ruling HQ H350722 (January 16, 2026) held that an unlicensed online platform is "impermissibly conducting customs business by ... deriving HTSUS subheading suggestions beyond the six-digit level via its AI classification tool if the merchandise being classified will be entered". A disclaimer does not change that (HQ H290535).

CBP ruling HQ 114654 draws the line: unlicensed persons "may explain the use of the Harmonized Tariff Schedules", but "may not, however, advise a client on how to classify ... merchandise that is going to be the subject of an entry".

An importer may classify its own goods. So htsapi.dev gives an importer's own AI agent the sources and the method, and the importer decides. Our own classifier, offered as a second opinion, returns guidance, not a determination for entry.

This is our reading of CBP's rulings, not legal advice. A review by a customs attorney is pending.