AI HTS Classification: How It Works vs Rule-Based Systems (2026)

AI classification uses an AI agent that searches over 220,000 CBP ruling precedents to classify products by understanding natural-language descriptions. Rule-based systems rely on brittle keyword matching and static decision trees that fail on novel products.

The Problem with Manual and Rule-Based Classification

The US Harmonized Tariff Schedule contains over 20,000 unique 10-digit codes, revised multiple times per year by the USITC. Every product entering the United States must be assigned one. Getting it wrong means overpaying duties, underpaying and facing CBP penalties, or shipment delays at the port.

Rule-based classification systems attempt to solve this with keyword matching: map "headphones" to 8518.30, "t-shirt" to 6109.10, and so on. This works for common products with obvious mappings. It fails everywhere else:

• Novel products. A "smart fitness ring with SpO2 sensor" has no keyword match. Is it jewelry (7117)? A medical instrument (9018)? An electrical apparatus (8543)?
• Ambiguous descriptions. "Plastic container" could be 3923 (transport/packing), 3924 (household), or 7010 (glass with plastic coating). Keywords alone can't disambiguate.
• Constant revisions. The USITC issues multiple revisions per year. Rule-based systems require manual updates for each one.
• Material/function interactions. GRI rules dictate that classification depends on essential character, principal use, or material composition. Keywords can't reason about these.

Manual classification by trained staff costs $100-200 per classification at consulting rates. Training a new classifier takes weeks to months. Licensed customs broker exams have pass rates in the single digits to ~30% per sitting.

How AI Classification Works (htsapi.dev Architecture)

htsapi.dev uses an agent-based architecture: an LLM with access to specialized tools, rather than a single-pass model. The agent decides which tools to use based on the query.

Step 1: Search CBP rulings for precedent

The agent searches over 220,000 CBP CROSS rulings for products substantially similar to the query. These are real classification decisions made by U.S. Customs and Border Protection -- the strongest available evidence for how a product should be classified.

Step 2: If ruling matches, follow CBP precedent

When the agent finds a relevant ruling, it follows the classification that CBP assigned. This is not the AI's opinion -- it's the government's actual decision on a similar product. The ruling number is cited in the response so users can verify it.

Step 3: If no ruling, reason from the tariff schedule

When no ruling exists, the agent reads the relevant sections of the HTS schedule, applies General Rules of Interpretation (GRI), checks chapter and section notes, and verifies the classification against adjacent headings to ensure it's the most specific match.

Step 4: Commit or ask for clarification

The agent commits a classification with a confidence level (high, medium, low). If the answer depends on an unknown attribute -- material composition, intended use, method of construction -- the agent asks a specific clarification question instead of guessing.

AI vs Rule-Based: Feature Comparison

What Makes CBP Ruling Evidence Different

Most classification tools generate an answer from a model. htsapi.dev finds the answer CBP already gave for a similar product. The difference is authority: a CBP ruling is a government agency's actual classification decision, not an algorithm's best guess.

Example: "Smart fitness ring with heart rate and SpO2"

The agent finds CBP ruling N306418 (Everion Fitness Monitor -- a wrist-worn device measuring heart rate, SpO2, blood pressure). CBP classified it under 9031.80.8085 (measuring/checking instruments, not elsewhere specified). The agent follows this precedent and cites the ruling in its response.

A rule-based system would try to match "ring" (jewelry?) or "heart rate" (medical?) and likely return the wrong code or no result.

Example: "Cat 6 LAN cables, 10 feet, unshielded"

The agent finds 5 CBP rulings for ethernet/LAN cables, all pointing to 8544.49.3080 (electric conductors, for a voltage not exceeding 80V, fitted with connectors). With multiple rulings converging on the same code, the agent commits with high confidence.

When AI Classification Asks for Clarification

Rule-based systems either return a result or fail silently. They don't know what they don't know. AI classification identifies the specific attribute that would change the outcome and asks for it.

Real examples from the API:

• "Cotton shirt" -- "Is the shirt knit or woven?" (Knit = Chapter 61, Woven = Chapter 62. The duty rate difference can be 10+ percentage points.)
• "Water pump" -- "Is the pump electric or mechanical? What is the flow rate?" (Electric pumps go to 8413, mechanical to different headings depending on type.)
• "Plastic container" -- "Is this for transport/packing of goods, or for household use?" (3923 vs 3924 -- different headings, different duties.)
• "LED light" -- "Is this for motor vehicles, or general illumination?" (8512 vs 9405 -- entirely different chapters.)

The system only asks when the answer would change the HTS code. If the description is specific enough to classify unambiguously, it classifies directly.

Real-World Accuracy

On a 54-product test drawn from 2024+ CBP rulings (the source ruling hidden from the agent, 2 runs, 2026-10-01):

• 69-76% exact 10-digit code
• 83-89% right 6-digit subheading
• 85-91% right 4-digit heading

That is the only measurement of the current version. The accuracy page has the method and what high and medium confidence mean.

The remaining errors cluster in structurally hard categories:

• Chemicals with IUPAC names -- specialized nomenclature that doesn't map to tariff language
• Function-based classifications -- "parts suitable for use with machines of heading 84.71"
• Multi-material composites -- products requiring GRI 3 analysis to determine essential character

Responses also carry Census Bureau duty figures (by country, if you give one): what importers paid in the latest published month, at the 10-digit line when there is enough trade, else the 6-digit subheading, with the last 3 months shown and a 12-month average as a footnote. They include Section 301/232 duties actually paid. Past imports, not the duty a specific shipment will owe. For the duty the schedule sets, GET /v1/hts/{code} (free with a key) gives the base rate. The API does not compute the additional Chapter 99 duties (Section 301, 232 and others).

Data Sources

Getting Started

Try free on the web: The htsapi.dev demo runs the full classification pipeline. Describe any product, see the HTS code with confidence level, CBP ruling evidence, and duty rates. No signup or API key required.

API integration: One endpoint, $0.05/classification at the 1,000-credit tier.

curl -X POST https://htsapi.dev/v1/classify \
  -H "X-API-Key: YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"description": "smart fitness ring with SpO2 sensor"}'

Response leads with an answer (the code at the depth your facts support, plus options and a question when a fact is missing), then candidates with confidence, CBP ruling citations, schedule duty and Census duty figures. See the developer integration guide for Python and Node.js examples, response schema, and error handling.

Frequently Asked Questions