How Trade Core Works
You describe a product to Claude or ChatGPT in your own words. This skill's tools hand your assistant the official tariff text and the CBP rulings that decided products like yours — each with its ruling number, its date and the facts you would have to confirm. Your assistant picks the 10-digit code and shows its working. Here's how that works, where it is strong, and where you should verify.
The approach
The skill connects to your LLM workspace (Claude, ChatGPT, or any MCP-compatible environment) and provides tools for step-by-step tariff classification. There is no Proofwork application to log into and no form to fill in: you describe the product in the chat you already use. The server returns candidate headings with CBP ruling precedents, chapter notes, and classification instructions. Your assistant does the reasoning.
Proofwork is never in the inference path. The server handles deterministic work — candidate retrieval, evidence card construction, CROSS ruling lookup — while your assistant applies the GRI rules and selects the code. We never call a model, and we never see your conversation: the tools receive the arguments of each call and nothing else.
What comes back
You ask
What's the HTS code for an indoor security camera that records to a microSD card and has two-way talk?
The tool returns a precedent
classified “an indoor security camera system that captures and records video, has a MicroSD card slot, and includes a two-way talk intercom feature” under 8525.89.5050 — still a line of the bundled schedule.
Qualified: the ruling's text states a fact the description does not, so the match is reported as qualified rather than exact.
Facts to confirm
- Article: the ruling's product is "an indoor security camera system that captures and records video, has a MicroSD card slot, and includes a two-way talk intercom feature" — this product is it.
- Material or composition, construction or form, principal function or use, and any dimension, weight or value a 10-digit line splits on are as in the ruling.
- If one of these facts differs, the ruling does not settle it: classify from the tariff text and say which fact distinguishes the product.
Your assistant decides whether that ruling governs your goods. When none matches, the tools say so rather than dressing a coincidence up as a precedent.
What the tools draw on
- CBP CROSS ruling rows — real customs decisions used as precedent evidence at every step. Each row carries how far it was checked, and whether the code it cites is still a line of the current schedule. What ships, in detail.
- Evidence cards — each candidate heading arrives with ruling precedents and chapter-note excerpts, so your assistant reasons from real regulatory text rather than from memory.
- One narrowing step at a time — heading, then subheading, then the 10-digit code, each its own tool call with its own evidence, the way a customs broker works. You can see what your assistant was given at every point.
Where it is strong, and where to verify
When a CBP ruling for a closely matching product is in the reference data, the tools state that ruling's holding and the classification typically follows it. When nothing comparable is there, the tools say so plainly rather than dressing a loose match up as a precedent, and the answer is reasoned from the tariff text — which is lower-confidence. Either way the tools state what a ruling said, not whether its facts are true of your goods: check the distinguishing facts yourself, confirm against the current HTSUS, and seek a binding ruling from CBP for material shipments.
Benchmark status
97.2% accuracy
See how we measured thisMeasured on 21 September 2026: Claude Opus 5 driving these MCP tools, web search off, counted right only when all ten digits match, over the 143 scorable products of our 150-product test set. The two figures are the same run twice: once with the test products' own CBP rulings available to the tools, once with every one of them withheld.
An earlier accuracy figure on this site was withdrawn: the evaluation behind it let the tools retrieve the test products' own CBP rulings, the case count was overstated, and the customer-facing tool path had never been measured. The methodology page says exactly what was wrong, what changed so it cannot recur, which cases are excluded and why, the known failure modes, and the commands that reproduce both figures.
Your assistant can already search the web
So can everyone's. The question is not whether a search finds a customs ruling — it usually does. It is whether the ruling it found has been revoked, whether the code on it is still a line of the tariff schedule, and which of the articles in it the code actually belongs to. A search result does not say.
Web search alone
Measurement in progress
We have not run our benchmark with the tools switched off, so we do not have this number and will not guess at one. It goes here when it is measured.
What a search result does not tell you
-
A ruling can be findable and still be dead
2 benchmark answers that rested on revoked rulings.
Source:
docs/BENCHMARK-AUDIT-2026-09.md -
A ruling's code can be gone from the schedule
of the ruling rows we ship cite a 10-digit code the current schedule no longer has.
Source:
proofwork/skills/hts/data/cross_build_stats.json, commit a1b4902 -
The summary you find may not match the ruling
7.3% of sampled summary rows cited a code their own ruling does not hold (6 of 82 rows; the sample puts the real rate between 3.4% and 15.1%).
Source:
proofwork/skills/hts/data/legacy_row_audit.json -
Search is very good at finding the answer to a published case
135 of 149 benchmark cases where the case's own source ruling turned up in the model's search results.
Source:
eval/results/agent-runs/telemetry-2026-09-20/REPORT.md, docs/SESSION-HANDOFF.md -
A search is not reproducible; this is
every row carries a provenance level and a corpus fingerprint.
Source:
proofwork/skills/hts/cross_corpus.py, proofwork/skills/hts/data/cross_manifest.json
None of this makes search useless — it is how you check us. It makes search a starting point rather than an answer.
Available tools
Your LLM calls these tools in sequence. Each step narrows the classification and provides evidence for the next decision.
Find the 4-digit HTS heading from candidate evidence cards
identify_heading_payload
Pick the 6-digit subheading from group evidence
select_subheading_payload
Pick the exact 10-digit code from leaf codes + precedents
select_leaf_payload
Compare selected code against sibling codes
verify_code_payload
Extract tariff-critical attributes from a product description
extract_tariff_attributes
Browse the labeled code tree for any heading
get_suffix_tree
Inspect available codes under any heading
explore_hts_heading
Ready to try it?
Add one URL to Claude or ChatGPT and ask about your first product in under a minute.
Get started