Claude connector guide
How to Connect Tariff Code Compliance to Claude and Classify Your First Product
Open the public connector listing, sign in to Tariff Code Compliance, and ask Claude to research a product against the tariff system and version available at that moment.
Connect Tariff Code Compliance
- Open Claude and go to Customize, then Connectors.
- Browse the directory and select Tariff Code Compliance.
- Review the listing and choose Connect.
- Sign in to Tariff Code Compliance, or create an account, in the Auth0 window.
- Review the requested read access to Tariff Code Compliance's tariff knowledge graph and approve the connection.
These steps match Anthropic's current connector instructions. A Team or Enterprise workspace may require an administrator to make a connector available first. Do not paste an access token into Claude; use the normal sign-in window.
Start with one self-contained request
The connector is enough for your first classification. Replace the two bracketed placeholders with a real product and its import destination. The request tells Claude to ask only for missing facts that could change the result, then use the connector to research current tariff evidence.
First request
Classify this product for import into [destination country or customs territory]:
[product description]
Ask the user for the import destination if it was omitted. Ask the user for the entire product description if it was omitted. Then ask only for any other missing product facts that could change the classification. Use Tariff Code Compliance to discover the currently enabled tariff system that covers the destination and its exact active version, then research the relevant classification nodes and graph evidence. Return the tariff system and exact version, recommended code and description, product facts used, supporting evidence, rejected alternatives and why they do not fit, assumptions, and remaining uncertainty. If the destination is not covered or the facts or evidence are insufficient, return the unresolved candidates and focused follow-up questions instead of forcing a code.
Tariff Code Compliance tools only read tariff evidence. Treat the recommendation as non-binding research support, not legal advice or a binding customs ruling. The user decides whether and how to use it.
Keep this response focused on classification. Do not include duty rates, fees, taxes, landed cost, or calculations of those amounts.
Use only the customer-facing `reference` and `references` fields returned by Tariff Code Compliance when naming graph evidence. For every relevant recommended, ancestor, candidate, or rejected code and every decisive note, exclusion, term, or annotation, render a Markdown link in the exact form `[<reference.label>](<reference.url>)` only when `reference.url` is present, substituting both values verbatim from that returned reference. When `reference.url` is absent, show `reference.label` as plain text with readable official provenance; never guess or hand-build a link. Never print or transform node IDs, `system_version_id`, source or storage keys, UUIDs, or page or continuation tokens, including values beginning `ent:`, `sysv:`, or `NATIONAL_`. If an entity-specific reference is unavailable, use the returned exact system/version reference under the same URL-present rule; do not expose the opaque value.Do not hard-code a tariff revision into a reusable request; tariff schedules change. If you want the same behavior as a reusable workflow, the published Classify Product skill is available, but it is optional and is not required to use the connector.
Check the evidence, not just the code
A useful result names the tariff system and version, the product facts used, relevant hierarchy or notes, plausible alternatives, why each alternative was rejected, and any remaining uncertainty. If a controlling fact is missing, Claude should ask a focused question instead of forcing a code.
Claude conducts the conversation and assembles the recommendation. Tariff Code Compliance for Claude supplies read-only access to requested tariff-knowledge-graph evidence. The recommendation is non-binding research support, not legal advice or a binding customs ruling, and the user decides whether and how to use it.
Continue the Claude classification series
- Learn what Claude can and cannot do with HS codes.
- Compare Claude alone, Tariff Code Compliance for Claude, and a customs broker.
- Follow the complete cotton T-shirt HTS walkthrough.
- Read the canonical agent guide and MCP documentation.
- Inspect public tariff data in the Tariff Code Compliance Explorer.
Research your first product
Open the public listing, connect your Tariff Code Compliance account, and ask Claude to discover the current tariff system before it researches a code.