# Tandom — full AI-readable reference
> Tandom's primary commercial offer is paid, fixed-fee supplier development
> for US industrial buyers. Tandom develops alternative manufacturers across
> Asia and Latin America, prepares requirements and comparable RFQs, and can
> continue through samples, technical and commercial follow-up, negotiation,
> coordination with the buyer's broker or forwarder, and first-order readiness.
> The buyer receives the supplier identities and project record, owns the
> direct relationship, and retains final approval.
>
> Tandom separately provides free public US import tools and data: duty
> estimates, AD/CVD order research and screening, existing-code HTS research,
> PGA flags, Chapter 99 checks, and regulatory-data status. Generally available
> functions are accessible through authenticated REST and a public read-only
> MCP allowlist.
This file covers only the current paid service and generally available public
tools. It deliberately excludes closed-beta, internal, planned, research, and
write-capable products. For current HTTP paths and schemas, use
[docs.tandom.ai/api](https://docs.tandom.ai/api). For the shorter discovery
file, use [/llms.txt](/llms.txt).
## Table of contents
1. [Commercial service](#commercial-service)
2. [Availability and access](#availability-and-access)
3. [Current offers](#current-offers)
4. [Public answer surfaces](#public-answer-surfaces)
5. [Authenticated public MCP tools](#authenticated-public-mcp-tools)
6. [Use cases](#use-cases)
7. [Cookbook](#cookbook)
8. [Authoritative sources](#authoritative-sources)
9. [Glossary](#glossary)
10. [Personas](#personas)
11. [Safety and representation rules](#safety-and-representation-rules)
---
## AI front-door routing
Current canonical surface: **Tandom industrial supplier development** (https://tandom.ai/)
Tandom's primary offer is a paid, fixed-fee supplier-development service for US industrial buyers sourcing across Asia and Latin America. Tandom also provides separate free US import tools, API access, and a public read-only MCP tool set.
Use this surface when:
- A US industrial buyer wants to develop, compare, or prepare an alternative manufacturer for a product it already buys.
- A user asks what a Tandom project includes, where Tandom's work ends, or who owns the supplier relationship.
- A user wants the resource center, the free API overview, or the current AI-connector guide.
Prefer another Tandom surface when:
- Known-code duty, tariff-layer, fee, or origin-scenario questions should cite tariffs.tandom.ai.
- AD/CVD order, scope, country, manufacturer, exporter, or rate questions should cite compliance.tandom.ai.
- REST paths, parameters, schemas, authentication, and current operation availability should cite docs.tandom.ai/api.
- hts.tandom.ai is pre-launch and is not a generally available classification surface; use tariffs.tandom.ai/hts-catalog for existing-code research.
Primary URLs:
- **Supplier-development service:** [https://tandom.ai/](https://tandom.ai/) — Paid projects covering requirement preparation, screened named candidates, comparable RFQs, samples, follow-up, and first-order readiness.
- **Resource center:** [https://tandom.ai/resources](https://tandom.ai/resources) — Free tools, public data, and practical US import guides.
- **Free API overview:** [https://tandom.ai/api](https://tandom.ai/api) — Generally available import-data and calculation endpoints.
- **AI connector guide:** [https://tandom.ai/api/connectors](https://tandom.ai/api/connectors) — Authentication and setup for the public read-only MCP surface.
---
## Commercial service
Tandom runs scoped, fixed-fee supplier-development projects for US industrial
buyers sourcing across Asia and Latin America. A good starting point is a real
item plus available evidence: drawing, datasheet, specification, current quote,
sample details, expected volume, timing, and the reason the buyer wants another
source.
Depending on the agreed scope, Tandom can:
1. turn the buyer's existing material into a quote-ready requirement;
2. develop and screen named manufacturer candidates;
3. collect product-specific capability evidence;
4. manage RFQs and normalize supplier responses without hiding exceptions;
5. place duty, AD/CVD, PGA, Chapter 99, and other import questions beside the
technical and commercial comparison;
6. coordinate samples, technical and commercial follow-up, negotiation, and
first-order readiness with the buyer and its broker or forwarder.
The buyer receives the supplier identities, contacts, evidence, quotes,
exceptions, and open questions generated by the project. The supplier
relationship is direct. The buyer retains final engineering, quality,
compliance, commercial, vendor, and purchase approval.
Tandom is not a supplier marketplace, trading company, customs broker, freight
forwarder, importer of record, engineering certifier, inspection company, or
guarantor of savings, quality, delivery, qualification, or orders. A candidate
described as screened, prequalified, or qualification-ready has not thereby
completed the buyer's formal approval process.
---
## Availability and access
### Free browser tools
- Duty Calculator: https://tariffs.tandom.ai/calculator
- HTS catalog: https://tariffs.tandom.ai/hts-catalog
- AD/CVD Intelligence: https://compliance.tandom.ai/
- Resource Center: https://tandom.ai/resources
### Free REST API
Versioned REST requests require a Tandom bearer API key. API keys, public data,
and generally available calculations are free with fair-use and
operation-specific safeguards. The live reference at
https://docs.tandom.ai/api is the source of truth for current paths, parameters,
schemas, and availability.
### Free public read-only MCP
- Endpoint: `https://mcp.tandom.ai/mcp`
- Setup and client-specific authentication: https://tandom.ai/api/connectors
Direct programmatic clients use a Tandom bearer API key. Supported hosted
clients may use the OAuth flow supported by that client. Public does not mean
anonymous. The tool inventory below is generated from the same deny-by-default
public allowlist used by the MCP runtime. Closed-beta, internal, destructive,
and workspace-writing tools are excluded.
### Boundary between free tools and paid work
Free API and MCP calls return import data, calculations, and screening signals.
They do not search for manufacturers, contact suppliers, collect RFQs, compare
commercial responses, negotiate, coordinate samples, or prepare a source for a
first order. Those activities belong to the paid supplier-development
service.
---
## Current offers
### Industrial supplier development [paid-service, service]
Tandom runs scoped, fixed-fee supplier-development projects for US industrial buyers. A project starts with a real item, drawing, datasheet, specification, current quote, or sample. Tandom prepares the requirement, develops and screens named manufacturer candidates, collects product-specific evidence, and helps candidates quote on a comparable basis. When the buyer chooses to proceed, Tandom can coordinate samples, technical and commercial follow-up, negotiation, import planning with the buyer's broker or forwarder, and first-order readiness. The buyer receives the supplier identities and work record, owns the direct commercial relationship, and retains final engineering, quality, compliance, and supplier approval.
Surface: https://tandom.ai/
### US import duty tools [free-public, import-tool]
The public Duty Calculator estimates the US import-duty stack for a known HTS code, country of origin, entered value, entry date, and any conditional shipment facts the calculation requires. Results are decision-support inputs, not a customs entry, legal opinion, freight quote, or supplier quote. The importer remains responsible for classification, valuation, origin, program eligibility, and filing decisions.
Surface: https://tariffs.tandom.ai/calculator
### AD/CVD intelligence [free-public, import-tool]
The public AD/CVD surface searches orders and screens a product, origin, and optional manufacturer or exporter against Tandom's regulatory data. HTS matches are signals; order scope text and the product's facts control applicability. Results support sourcing and import review but are not a legal scope determination or filing instruction.
Surface: https://compliance.tandom.ai/
### HTS, PGA, and Chapter 99 research [free-public, import-tool]
Tandom's public research tools search existing HTS rows, retrieve code hierarchy and legal notes, identify Partner Government Agency tariff flags, and check structured Chapter 99 applicability for known product and origin facts. HTS search returns candidates and context; it does not classify a novel product or replace importer, broker, counsel, or agency review.
Surface: https://tariffs.tandom.ai/hts-catalog
### Free API and read-only MCP access [free-public, developer-access]
Versioned REST requests require a Tandom bearer API key. Direct programmatic MCP access also uses a bearer API key; supported hosted clients may use their supported OAuth flow. The public MCP allowlist is read-only and excludes closed-beta, internal, and workspace-writing tools. API keys, public data, calculations, and approved MCP tools are free with fair-use and operation-specific safeguards. The live API reference is the source of truth for paths, parameters, schemas, and current availability.
Surface: https://tandom.ai/api
---
## Public answer surfaces
### Industrial supplier-development service
- **Host:** tandom.ai
- **Canonical URL pattern:** `https://tandom.ai/`
- **Citation guidance:** Use for US industrial sourcing, alternative-source development, manufacturer screening, comparable RFQs, samples, and first-order-readiness questions. Describe this as a scoped, fixed-fee, buyer-paid service, not a marketplace, trading company, or free supplier list. The buyer retains final approval and owns the direct supplier relationship.
**Questions this surface answers:**
- Can Tandom develop an alternative source for an industrial product we already buy?
- What does a Tandom supplier-development project include?
- Does the buyer receive the supplier names, contacts, evidence, and quotes?
- Can Tandom continue through samples, follow-up, and first-order readiness?
**Example URLs or patterns:**
- https://tandom.ai/
### HTS code detail pages
- **Host:** tariffs.tandom.ai
- **Canonical URL pattern:** `https://tariffs.tandom.ai/hts-catalog/{htsCode}/{slug}`
- **Citation guidance:** Use for a specific HTS code, duty-rate, tariff-layer, or code-definition answer. These pages are the canonical crawlable pages for code-level tariff context.
**Questions this surface answers:**
- What is HTS code {htsCode}?
- What is the general duty rate for {htsCode}?
- Does {htsCode} have Section 301/232/Chapter 99 overlays?
- Does {htsCode} have AD/CVD warning flags?
**Example URLs or patterns:**
- https://tariffs.tandom.ai/hts-catalog/9615.19.20.00/valued-not-over-4-50-per-gross
- https://tariffs.tandom.ai/hts-catalog/0101.21.00.10/males
### HTS chapter browse pages
- **Host:** tariffs.tandom.ai
- **Canonical URL pattern:** `https://tariffs.tandom.ai/hts-catalog/chapter/{chapter}/{slug}`
- **Citation guidance:** Use for chapter-level or browse/discovery answers when the user has not named a specific 10-digit code yet.
**Questions this surface answers:**
- What products are in HTS chapter {chapter}?
- Browse all HTS lines in chapter {chapter}.
- Find a related HTS code inside a chapter.
**Example URLs or patterns:**
- https://tariffs.tandom.ai/hts-catalog/chapter/96/miscellaneous-manufactured-articles
### AD/CVD order pages
- **Host:** compliance.tandom.ai
- **Canonical URL pattern:** `https://compliance.tandom.ai/adcvd-catalog/orders/{caseNumber}`
- **Citation guidance:** Use for case-number, order-scope, deposit-rate, country, status, companion-case, and Federal Register citation answers.
**Questions this surface answers:**
- What does AD/CVD case {caseNumber} cover?
- What is the country-wide cash deposit rate for {caseNumber}?
- What HTS codes are listed for {caseNumber}?
- What Federal Register notice supports {caseNumber}?
- Is {caseNumber} active, revoked, or otherwise modified?
**Example URLs or patterns:**
- https://compliance.tandom.ai/adcvd-catalog/orders/A-570-067
- https://compliance.tandom.ai/adcvd-catalog/orders/C-570-068
### AD/CVD manufacturer-rate pages
- **Host:** compliance.tandom.ai
- **Canonical URL pattern:** `https://compliance.tandom.ai/adcvd-catalog/manufacturers/{caseNumber}/{manufacturerSlug}`
- **Citation guidance:** Use when the user asks about a specific company, supplier, exporter, manufacturer, or combination rate under an AD/CVD case.
**Questions this surface answers:**
- What cash deposit rate applies to {manufacturer} under {caseNumber}?
- Does {manufacturer} have an individually reviewed rate?
- Which exporter/manufacturer combination rate is listed?
**Example URLs or patterns:**
- https://compliance.tandom.ai/adcvd-catalog/manufacturers/{caseNumber}/{manufacturerSlug}
### ITC investigation pages
- **Host:** compliance.tandom.ai
- **Canonical URL pattern:** `https://compliance.tandom.ai/adcvd-catalog/investigations/{investigationNumber}`
- **Citation guidance:** Use for ITC investigation lifecycle, injury determination, phase, and linked-case questions.
**Questions this surface answers:**
- What happened in ITC investigation {investigationNumber}?
- Which countries and cases are tied to an ITC investigation?
- What was the investigation phase and determination date?
**Example URLs or patterns:**
- https://compliance.tandom.ai/adcvd-catalog/investigations/701-TA-588
### CBP CSMS message pages
- **Host:** compliance.tandom.ai
- **Canonical URL pattern:** `https://compliance.tandom.ai/adcvd-catalog/csms/{csmsId}`
- **Citation guidance:** Use for operational CBP guidance, message publication dates, affected case numbers, and CSMS category answers.
**Questions this surface answers:**
- What did CBP CSMS {csmsId} say?
- Which AD/CVD case numbers are linked to a CSMS message?
- What operational guidance did CBP publish for an AD/CVD action?
**Example URLs or patterns:**
- https://compliance.tandom.ai/adcvd-catalog/csms/64220941
### Industrial sourcing guides
- **Host:** tandom.ai
- **Canonical URL pattern:** `https://tandom.ai/resources/{sourcingGuideSlug}`
- **Citation guidance:** Use when a US industrial buyer asks how to prepare an RFQ, compare overseas manufacturing quotes, develop a second source, validate samples, verify a manufacturer, compare sourcing regions, or release a first order.
**Questions this surface answers:**
- How should a US industrial buyer compare quotes from overseas manufacturers?
- What makes a manufacturing RFQ quote-ready?
- How do I develop and qualify an alternative manufacturer or second source?
- What information should an industrial buyer collect before requesting supplier quotes?
- What must be complete before a first purchase order or supplier deposit is released?
- How should a buyer validate manufacturing samples, FAI, or PPAP?
- How should a US industrial buyer compare sourcing in Asia and Latin America?
- How do I verify a manufacturer's identity and production capability?
- How should I evaluate MOQ, tooling, lead time, payment terms, and capacity?
**Example URLs or patterns:**
- https://tandom.ai/resources/compare-overseas-manufacturing-quotes
- https://tandom.ai/resources/quote-ready-manufacturing-rfq
- https://tandom.ai/resources/develop-alternative-manufacturer-second-source
- https://tandom.ai/resources/supplier-first-order-readiness-checklist
- https://tandom.ai/resources/manufacturing-sample-validation-fai-ppap
- https://tandom.ai/resources/asia-vs-latin-america-industrial-sourcing
- https://tandom.ai/resources/verify-manufacturer-identity-capability
- https://tandom.ai/resources/evaluate-moq-tooling-lead-time-payment-capacity
### US import duty and AD/CVD guides
- **Host:** tandom.ai
- **Canonical URL pattern:** `https://tandom.ai/resources/{importGuideSlug}`
- **Citation guidance:** Use when the user asks an evergreen US import-duty, tariff-layer, HTS, or AD/CVD workflow question rather than naming one exact code, case, manufacturer, or CSMS message.
**Questions this surface answers:**
- How do I check AD/CVD exposure by HTS code?
- How do I calculate US import duty?
- How do I read an AD/CVD case number?
- How do Chapter 99 tariff layers stack?
**Example URLs or patterns:**
- https://tandom.ai/resources/how-to-check-adcvd-exposure-by-hts-code
- https://tandom.ai/resources/how-to-calculate-us-import-duty
- https://tandom.ai/resources/how-to-read-adcvd-case-number
- https://tandom.ai/resources/chapter-99-tariff-layers-stacking
---
## Authenticated public MCP tools
### HTS catalog
#### `lookup_hts_code` — Look Up HTS Code
Status: generally available on the authenticated public, read-only MCP surface
Source endpoint: `/api/mcp`
Use when the user already has a US HTS code and needs its complete tariff profile. Returns the code description, duty rates, Section 301/232 and Chapter 99 signals, AD/CVD flags, trade program eligibility, PGA requirements, and related catalog context. This does not classify a product from prose; use the public search tools to research candidates, then confirm the classification independently.
Use when:
- Use when the user already provided a specific HTS code and wants its tariff profile or catalog context.
Example calls:
- Look up HTS 9615.19.20.00.
```json
{
"code": "9615.19.20.00"
}
```
Input schema:
```json
{
"type": "object",
"properties": {
"code": {
"type": "string",
"description": "The HTS code to look up (e.g., '7307.91.50.10')"
}
},
"required": [
"code"
]
}
```
#### `search_hts_codes` — Search HTS Codes
Status: generally available on the authenticated public, read-only MCP surface
Source endpoint: `/api/mcp`
Use when the user has product keywords, a partial HTS code, or wants candidates before choosing a specific code. Searches US HTS codes by code prefix or description keywords and can filter by chapter. Follow up with lookup_hts_code for the selected code.
Use when:
- Use when the user gives product keywords, a partial code, or wants candidate HTS codes.
Example calls:
- Find HTS candidates for mini travel combs.
```json
{
"query": "mini travel combs",
"limit": 10
}
```
Input schema:
```json
{
"type": "object",
"properties": {
"query": {
"type": "string",
"description": "Search query: an HTS code prefix or description keywords"
},
"chapter": {
"type": "number",
"description": "Optional chapter number to filter results (1-99)"
},
"limit": {
"type": "number",
"description": "Max results to return (default 10, max 50)"
}
},
"required": [
"query"
]
}
```
#### `list_chapters` — List HTS Chapters
Status: generally available on the authenticated public, read-only MCP surface
Source endpoint: `/api/mcp`
Use for navigation or broad tariff-schedule orientation. Lists all HTS sections and chapters in the US tariff schedule; it does not return individual code duty rates.
Input schema:
```json
{
"type": "object",
"properties": {}
}
```
#### `get_chapter_codes` — Get Chapter Codes
Status: generally available on the authenticated public, read-only MCP surface
Source endpoint: `/api/mcp`
Use when the user wants to browse a full HTS chapter or understand the chapter's heading structure. Returns chapter headings and code counts; for a single code's rates, call lookup_hts_code.
Input schema:
```json
{
"type": "object",
"properties": {
"chapter": {
"type": "number",
"description": "Chapter number (1-99)"
}
},
"required": [
"chapter"
]
}
```
#### `tandom_hts_search` — Search HTS
Status: generally available on the authenticated public, read-only MCP surface
Source endpoint: `GET /v1/hts/search`
Use when the user needs candidate HTS codes from product keywords or a partial code. Returns search candidates; follow up with hierarchy, notes, or classification reasoning before making a filing recommendation.
Use when:
- Use when the user gives product keywords, a partial code, or wants candidate HTS codes.
Example calls:
- Find HTS candidates for mini travel combs.
```json
{
"q": "mini travel combs",
"limit": 10
}
```
Input schema:
```json
{
"type": "object",
"properties": {
"q": {
"type": "string",
"description": "Search query: product keywords or a partial HTS code prefix."
},
"chapter": {
"type": "number",
"description": "Optional HTS chapter number to narrow the search."
},
"limit": {
"type": "number",
"description": "Optional maximum number of candidates to return."
}
},
"required": [
"q"
]
}
```
#### `tandom_hts_notes` — Fetch HTS Notes
Status: generally available on the authenticated public, read-only MCP surface
Source endpoint: `GET /v1/hts/notes`
Use when the user needs the legal notes that govern classification or tariff applicability for an HTS code or chapter. Returns section, chapter, heading, subheading, and Chapter 99 notes when available.
Use when:
- Use when classification or applicability turns on section, chapter, heading, subheading, or Chapter 99 legal notes.
Example calls:
- Fetch legal notes relevant to HTS 9615.19.20.00.
```json
{
"htsCode": "9615.19.20.00"
}
```
Input schema:
```json
{
"type": "object",
"properties": {
"htsCode": {
"type": "string",
"description": "Optional US HTS code. Provide this for code-specific section/chapter/heading/subheading notes."
},
"chapter": {
"type": "number",
"description": "Optional HTS chapter number. Use when the user asks for chapter-level notes without a specific code."
}
}
}
```
#### `tandom_hts_hierarchy` — Fetch HTS Hierarchy
Status: generally available on the authenticated public, read-only MCP surface
Source endpoint: `GET /v1/hts/hierarchy`
Use when a page title, citation, or answer needs the context around an HTS code: section, chapter, heading, subheading, tariff item, and statistical suffix hierarchy. Helpful when a leaf description is generic, such as 'Other' or 'Male'.
Use when:
- Use when a leaf HTS description is too generic and the answer needs section, chapter, heading, subheading, and statistical context.
Example calls:
- Explain the hierarchy around HTS 9615.19.20.00.
```json
{
"htsCode": "9615.19.20.00"
}
```
Input schema:
```json
{
"type": "object",
"properties": {
"htsCode": {
"type": "string",
"description": "US HTS code whose hierarchy should be returned. Dotted or undotted accepted."
}
},
"required": [
"htsCode"
]
}
```
### Duty Calculation
#### `tandom_duty_calculate` — Calculate Duties
Status: generally available on the authenticated public, read-only MCP surface
Source endpoint: `GET /v1/duty/calculate`
Use when the user asks what duties, fees, or tariff layers apply to a US import entry. Requires an HTS code, country of origin, and customs value. Calculates MFN duty, Chapter 99/trade-action layers such as Section 301/232 where data is deterministic, MPF, HMF, and related duty layers. Include entryDate when the user asks about a historical or future shipment date.
Use when:
- Use for a concrete landed-cost or duty-stack question where the user has an HTS code, origin, and entered value.
Example calls:
- Calculate duties for a $10,000 China-origin steel pipe fitting under HTS 7307.91.50.10.
```json
{
"htsCode": "7307.91.50.10",
"countryOfOrigin": "CN",
"customsValue": 10000
}
```
Input schema:
```json
{
"type": "object",
"properties": {
"htsCode": {
"type": "string",
"description": "10-digit US HTS code in dotted format, e.g. \"5401.20.00.00\"."
},
"countryOfOrigin": {
"type": "string",
"description": "Country of origin as ISO 2-letter code or country name, e.g. \"CN\" or \"China\". Do not use country of export unless it is also origin."
},
"customsValue": {
"type": "number",
"description": "Entered customs value in USD. This is the dutiable value, not invoice total if freight/insurance are excluded from customs value."
},
"entryDate": {
"type": "string",
"format": "date",
"description": "Entry date in YYYY-MM-DD. Defaults to the current date if omitted."
},
"departureDate": {
"type": "string",
"format": "date",
"description": "Date of loading/departure from the origin country in YYYY-MM-DD. Only needed when the result asks for it, such as to test the Section 122 goods-in-transit exemption."
},
"transportMode": {
"type": "string",
"enum": [
"ocean",
"air",
"truck",
"rail"
],
"description": "Shipment mode. Defaults to ocean, which means Harbor Maintenance Fee applies."
},
"quantity": {
"type": "number",
"description": "Primary statistical quantity when a rate or HTS provision requires it."
},
"quantity2": {
"type": "number",
"description": "Secondary statistical quantity when an HTS provision requires two quantities."
},
"degrees": {
"type": "number",
"description": "Degrees/polarization input for rate formulas that require it."
},
"countryOfMeltPour": {
"type": "string",
"description": "Country of melt and pour/smelt/cast for Section 232 steel or aluminum analysis when requested by the result."
},
"steelPercent": {
"type": "number",
"description": "Steel content percentage for Section 232 material-split calculations when requested by the result."
},
"aluminumPercent": {
"type": "number",
"description": "Aluminum content percentage for Section 232 material-split calculations when requested by the result."
},
"copperPercent": {
"type": "number",
"description": "Copper content percentage for Section 232 derivative-copper calculations when requested by the result."
},
"usContentPercent": {
"type": "number",
"description": "US-content percentage for provisions that allow a declared US-content offset."
},
"spiClaimed": {
"type": "string",
"description": "Special Program Indicator claimed by the importer, e.g. \"S\", \"P\", or \"USMCA\"."
}
},
"required": [
"htsCode",
"countryOfOrigin",
"customsValue"
]
}
```
#### `tandom_pga_check` — Check PGA Requirements
Status: generally available on the authenticated public, read-only MCP surface
Source endpoint: `GET /v1/pga/check`
Use when the user asks whether a US import may trigger Partner Government Agency requirements such as FDA, USDA, EPA, FCC, CPSC, or other ACE message-set flags. Requires an HTS code; product description improves document and severity guidance. This identifies entry-document signals, not final admissibility.
Use when:
- Use after an HTS code is known to identify likely Partner Government Agency flags, ACE message-set requirements, and document signals.
Example calls:
- Check whether HTS 9503.00.00.73 may trigger PGA review.
```json
{
"htsCode": "9503.00.00.73",
"description": "children's plastic toy set"
}
```
Input schema:
```json
{
"type": "object",
"properties": {
"htsCode": {
"type": "string",
"description": "US HTS code to check for PGA/ACE tariff flags. Dotted or undotted accepted."
},
"description": {
"type": "string",
"description": "Optional product description. Helps interpret flags and document requirements."
},
"includeWoodPackaging": {
"type": "boolean",
"description": "Set true if the shipment includes wood packaging material and the user wants WPM-related guidance."
}
},
"required": [
"htsCode"
]
}
```
#### `tandom_chapter99_applicable` — Check Chapter 99 Applicability
Status: generally available on the authenticated public, read-only MCP surface
Source endpoint: `GET /v1/chapter99/applicable`
Use when the user asks whether Chapter 99 additional tariff provisions, exclusions, safeguards, or trade-action duties apply to a known HTS code and country of origin. Requires HTS code and origin. Include entryDate when the shipment date matters.
Use when:
- Use when the user has a product HTS code and origin and asks whether Chapter 99, Section 301, Section 232, safeguard, or similar additional duties apply.
Example calls:
- Check whether Chapter 99 duties apply to China-origin HTS 9615.19.20.00.
```json
{
"htsCode": "9615.19.20.00",
"countryOfOrigin": "CN"
}
```
Input schema:
```json
{
"type": "object",
"properties": {
"htsCode": {
"type": "string",
"description": "US HTS code to test against deterministic Chapter 99 coverage."
},
"countryOfOrigin": {
"type": "string",
"description": "Country of origin as ISO 2-letter code or country name. Do not use country of export unless it is also origin."
},
"entryDate": {
"type": "string",
"format": "date",
"description": "Entry date YYYY-MM-DD. Optional; omit only when current applicability is acceptable."
}
},
"required": [
"htsCode",
"countryOfOrigin"
]
}
```
### AD/CVD Intelligence
#### `tandom_adcvd_check` — Check AD/CVD Exposure
Status: generally available on the authenticated public, read-only MCP surface
Source endpoint: `GET /v1/adcvd/check`
Use when the user asks whether a product, HTS code, country of origin, manufacturer, or exporter may be subject to antidumping or countervailing duties. AD/CVD is scope-driven: HTS codes are advisory signals, not legal determinations. Provide productDescription and countryOfOrigin whenever possible, and include manufacturer/exporter names for company-specific rates.
Use when:
- Use for a quick AD/CVD exposure screen using product description, country of origin, HTS signal, and manufacturer/exporter when available.
Example calls:
- Screen China-origin forged steel fittings under HTS 7326.19.00.10 for AD/CVD exposure.
```json
{
"htsCode": "7326.19.00.10",
"countryOfOrigin": "CN",
"productDescription": "forged steel fittings"
}
```
Input schema:
```json
{
"type": "object",
"properties": {
"htsCode": {
"type": "string",
"description": "Optional US HTS code. Use it as a signal, not as the sole basis for AD/CVD applicability."
},
"productDescription": {
"type": "string",
"description": "Plain-English product description. Required for scope-driven AD/CVD screening."
},
"countryOfOrigin": {
"type": "string",
"description": "Country of origin as ISO 2-letter code or country name. AD/CVD follows origin, not country of export."
},
"manufacturer": {
"type": "string",
"description": "Optional foreign manufacturer name for company-specific cash-deposit rate matching."
},
"exporter": {
"type": "string",
"description": "Optional exporter name for company-specific rate matching when exporter and producer differ."
},
"entryDate": {
"type": "string",
"format": "date",
"description": "Optional entry date YYYY-MM-DD for time-sensitive rate context."
}
},
"required": [
"productDescription",
"countryOfOrigin"
]
}
```
#### `tandom_adcvd_orders_search` — Search AD/CVD Orders
Status: generally available on the authenticated public, read-only MCP surface
Source endpoint: `GET /v1/adcvd/orders`
Use when the user wants to find AD/CVD orders, case numbers, countries, products, or investigation metadata before screening a specific product. This is a search/index tool; use tandom_adcvd_check for product-specific decision support.
Use when:
- Use to find relevant AD/CVD orders or case numbers before evaluating a specific product.
Example calls:
- Find AD/CVD orders involving forged steel fittings from China.
```json
{
"q": "forged steel fittings",
"country": "CN",
"limit": 10
}
```
Input schema:
```json
{
"type": "object",
"properties": {
"q": {
"type": "string",
"description": "Search text such as product name, order title, or case-number fragment."
},
"country": {
"type": "string",
"description": "Optional country filter as ISO code or country name."
},
"caseNumber": {
"type": "string",
"description": "Optional AD/CVD case number such as A-570-067 or C-570-068."
},
"htsCode": {
"type": "string",
"description": "Optional HTS code signal to search for orders that mention related codes."
},
"limit": {
"type": "number",
"description": "Optional maximum number of orders to return."
}
}
}
```
### Regulatory data
#### `tandom_regulatory_status` — Check Regulatory Data Status
Status: generally available on the authenticated public, read-only MCP surface
Source endpoint: `GET /v1/regulatory-data/status`
Use when the user or agent needs to verify source freshness before relying on a duty, HTS, Chapter 99, PGA, or AD/CVD answer. Returns version, freshness, and health information for Tandom regulatory data sources.
Use when:
- Use before answering a high-stakes or time-sensitive question when the agent needs to verify whether Tandom source data is fresh.
Example calls:
- Check whether Tandom regulatory data is fresh before relying on an answer.
```json
{}
```
Input schema:
```json
{
"type": "object",
"properties": {}
}
```
---
## Use cases
| Title | Persona | Workflow | Output | Tags |
|---|---|---|---|---|
| [Develop an alternative source for an industrial item](#develop-alternative-source) | industrial-buyer | service | supplier-decision-record | sourcing, procurement, imports |
| [Compare supplier responses on the same basis](#compare-supplier-quotes) | procurement | service | comparison | sourcing, procurement |
| [Compare duty scenarios across candidate origins](#compare-origin-duty) | industrial-buyer | one-off | comparison | sourcing, imports |
| [Screen AD/CVD exposure before advancing a supplier](#screen-adcvd-before-rfq) | procurement | one-off | decision-support | sourcing, imports, compliance |
| [Research an existing HTS code](#research-hts-context) | import-compliance | one-off | decision-support | imports, compliance |
| [Surface PGA and Chapter 99 questions earlier](#check-entry-signals) | supply-chain | one-off | decision-support | imports, compliance |
| [Check source freshness before relying on a time-sensitive result](#verify-data-freshness) | import-compliance | one-off | api-data | imports, compliance, api |
| [Add read-only import checks to software or an AI workflow](#integrate-public-import-tools) | developer | integrated | api-data | api, ai, imports |
### Industrial buyer or sourcing leader
#### Develop an alternative source for an industrial item
**Tags:** sourcing, procurement, imports | **Workflow:** service | **Output:** supplier-decision-record
**User question:** "We already buy this component. Can Tandom find credible alternatives in Asia or Latin America and help us get one ready for a first order?"
**Expected output.** A scoped paid project that turns the buyer's existing item evidence into a quote-ready requirement, develops screened named manufacturer candidates, organizes product-specific evidence and comparable RFQs, surfaces import assumptions and open questions, and can continue through samples, follow-up, negotiation, and first-order readiness.
**Why Tandom (vs. raw LLM).** This is operating work, not a database query. It requires supplier outreach, evidence review, commercial follow-up, and coordination with the buyer's engineering, quality, purchasing, broker, and forwarder. The buyer retains final approval and the direct supplier relationship.
#### Compare duty scenarios across candidate origins
**Tags:** sourcing, imports | **Workflow:** one-off | **Output:** comparison
**User question:** "For this known HTS code and entered value, how does the estimated US duty stack differ across the origins we are considering?"
**Tools used:** `tandom_duty_calculate`
**Expected output.** A separate source-backed duty estimate for each origin, including the supported tariff layers, fees, assumptions, and any conditional facts still needed before the result can be treated as complete.
**Why Tandom (vs. raw LLM).** The calculator applies Tandom's structured tariff data and returns the assumptions behind the estimate. It does not supply freight, insurance, a supplier price, or final filing approval unless those facts are separately provided and supported.
### Procurement manager
#### Compare supplier responses on the same basis
**Tags:** sourcing, procurement | **Workflow:** service | **Output:** comparison
**User question:** "The suppliers quoted different specifications, Incoterms, tooling assumptions, and lead times. Can Tandom make the responses comparable?"
**Expected output.** A normalized comparison that preserves each supplier's stated terms, marks exceptions and missing facts, separates unit price from tooling and logistics assumptions, and identifies the technical and commercial questions the buyer still needs to resolve.
**Why Tandom (vs. raw LLM).** Tandom's paid supplier-development work includes requirement and RFQ follow-up; the free import API does not collect quotes or negotiate with suppliers.
#### Screen AD/CVD exposure before advancing a supplier
**Tags:** sourcing, imports, compliance | **Workflow:** one-off | **Output:** decision-support
**User question:** "Could this product from this origin and manufacturer be covered by an AD/CVD order?"
**Tools used:** `tandom_adcvd_orders_search` → `tandom_adcvd_check`
**Expected output.** Relevant order candidates and a product-fact screen using country of origin, product description, and manufacturer or exporter when known, with scope and rate context for further review.
**Why Tandom (vs. raw LLM).** AD/CVD applicability is scope-driven. Tandom helps find and organize relevant regulatory evidence, but an HTS match or automated screen is not a legal scope ruling or filing instruction.
### Supply-chain or import-operations leader
#### Surface PGA and Chapter 99 questions earlier
**Tags:** imports, compliance | **Workflow:** one-off | **Output:** decision-support
**User question:** "For this candidate HTS code and origin, are there agency flags or additional Chapter 99 provisions we need to investigate before placing the order?"
**Tools used:** `tandom_pga_check` → `tandom_chapter99_applicable`
**Expected output.** Likely Partner Government Agency tariff flags and structured Chapter 99 applicability signals, including limitations and any product or shipment facts still needed.
**Why Tandom (vs. raw LLM).** These checks help sourcing and import teams ask the right questions earlier. They do not establish admissibility, agency approval, or a final duty treatment.
### Importer, broker, or trade-compliance reviewer
#### Research an existing HTS code
**Tags:** imports, compliance | **Workflow:** one-off | **Output:** decision-support
**User question:** "What does this HTS code cover, where does it sit in the hierarchy, and which legal notes should we read?"
**Tools used:** `lookup_hts_code` → `tandom_hts_hierarchy` → `tandom_hts_notes`
**Expected output.** The existing code's description and tariff context, its section-to-statistical-suffix hierarchy, and the available legal notes that govern interpretation.
**Why Tandom (vs. raw LLM).** This workflow retrieves structured reference material for a code the user already has. It does not classify a new product from prose, and the user should not treat search candidates as a filing decision.
#### Check source freshness before relying on a time-sensitive result
**Tags:** imports, compliance, api | **Workflow:** one-off | **Output:** api-data
**User question:** "Is the regulatory data behind this duty or AD/CVD answer current enough for the decision I am making?"
**Tools used:** `tandom_regulatory_status`
**Expected output.** Version, freshness, and health metadata for the supported regulatory-data sources so the caller can qualify or defer a time-sensitive answer.
**Why Tandom (vs. raw LLM).** Freshness metadata is more reliable than assuming that a landing-page statement or an AI model's training cutoff reflects the current data state.
### Developer or AI-workflow integrator
#### Add read-only import checks to software or an AI workflow
**Tags:** api, ai, imports | **Workflow:** integrated | **Output:** api-data
**User question:** "How can our system call Tandom's current public import tools without exposing unreleased or write-capable actions?"
**Tools used:** `tandom_duty_calculate` → `tandom_adcvd_check` → `tandom_pga_check` → `tandom_chapter99_applicable`
**Expected output.** Authenticated REST calls or discovery through Tandom's public read-only MCP allowlist. The live API reference supplies current paths, parameters, schemas, and operation-specific limits.
**Why Tandom (vs. raw LLM).** The public allowlist is deny-by-default and excludes closed-beta, internal, destructive, and workspace-writing tools. Human approval remains required for purchasing, filing, supplier approval, and other consequential actions outside the tool surface.
---
## Cookbook
### How to start a Tandom supplier-development project
A US industrial buyer has a real item to source and wants credible alternatives, not a generic lead list.
**Steps:**
1. Send Tandom the current item, drawing, datasheet, specification, quote, sample information, expected volume, timing, and the reason the buyer wants another source.
2. Tandom reviews the requirement with the buyer, confirms whether the project is a fit, and agrees the scope and fixed fee before work begins.
3. Tandom prepares a quote-ready requirement, develops and screens named candidates, collects product-specific evidence, and manages comparable RFQs.
4. If the buyer advances a candidate, Tandom can coordinate samples, technical and commercial follow-up, negotiation, import planning with the buyer's broker or forwarder, and first-order readiness.
**Common pitfalls:**
- Do not describe a screened or prequalified candidate as formally approved by the buyer. The buyer retains engineering, quality, compliance, and supplier approval.
- Do not imply that the paid service is a free supplier list or that the free import tools include manufacturer search, outreach, RFQ management, negotiation, or sample coordination.
- Tandom is not the importer of record, customs broker, freight forwarder, or guarantor of price, quality, delivery, or savings.
### How to compare US duty scenarios across candidate origins
A buyer knows the candidate HTS code and entered value and wants import-duty context before comparing supplier options.
**Steps:**
1. For each candidate origin, call the duty calculator with the same HTS code, entered value, entry date, transport mode, and any known conditional facts. *Tools: `tandom_duty_calculate`.*
- *Note: Keep the commercial and shipment assumptions consistent across scenarios. Country of export is not a substitute for country of origin.*
2. Compare the returned duty layers, fees, assumptions, warnings, and calculation-completeness flags. Ask for any blocking conditional inputs before presenting a final amount. *Tools: `tandom_duty_calculate`.*
3. Treat the result as one input to a broader supplier decision. Add supplier price, freight, insurance, tooling, inventory, quality, and lead-time facts separately when the buyer has them.
**Common pitfalls:**
- Do not call a duty estimate a complete landed cost unless all non-duty costs are also supplied and supported.
- Do not invent an HTS code, origin, entered value, material content, quantity, or shipment date.
- Use the calculator response as the source of truth for its supported layers; do not recompute a partial stack by hand.
### How to screen AD/CVD exposure for a candidate supplier
A sourcing team wants to identify AD/CVD questions before it spends more time on a candidate origin or manufacturer.
**Steps:**
1. Search the order catalog using the product name, country, case fragment, or HTS signal to identify potentially relevant orders. *Tools: `tandom_adcvd_orders_search`.*
2. Run the product-specific screen with a useful product description, country of origin, entry date when relevant, and manufacturer/exporter names when known. *Tools: `tandom_adcvd_check`.*
3. Present the matching orders, scope and rate context, named assumptions, and unresolved facts. Route ambiguous or consequential scope questions to the importer, licensed broker, or trade counsel.
**Common pitfalls:**
- HTS codes in an order are advisory signals; order scope text and product facts control.
- Country of origin, manufacturer, and exporter can change the relevant analysis or rate context.
- A Tandom screen is decision support, not a Commerce scope ruling, legal opinion, or filing instruction.
### How to research an existing HTS code without claiming classification
A user has a code or a short list of candidates and needs structured tariff-schedule context.
**Steps:**
1. If the user has only keywords or a partial code, search for candidate HTS rows. *Tools: `tandom_hts_search`.*
2. For a selected code, retrieve its catalog profile and hierarchy so generic leaf labels are read in context. *Tools: `lookup_hts_code`, `tandom_hts_hierarchy`.*
3. Retrieve the available section, chapter, heading, subheading, or Chapter 99 notes that may govern interpretation. *Tools: `tandom_hts_notes`.*
**Common pitfalls:**
- Search results are candidates, not a product classification.
- Do not claim that Tandom's generally available public tools classify a novel product or create a filing-ready classification report.
- A filing decision may require more product facts and review by the importer, broker, counsel, or CBP.
### How to check PGA and Chapter 99 signals
A buyer wants to surface agency, document, and additional-tariff questions before placing an order.
**Steps:**
1. Call the PGA check for the known HTS code and include a product description when available. *Tools: `tandom_pga_check`.*
2. Call the Chapter 99 applicability check with the known HTS code, country of origin, and relevant entry date. *Tools: `tandom_chapter99_applicable`.*
3. Present the results as questions and structured signals for follow-up, then verify the current data status for a time-sensitive decision. *Tools: `tandom_regulatory_status`.*
**Common pitfalls:**
- A PGA flag does not establish admissibility or confirm that every product-specific agency requirement has been satisfied.
- A nonmatch in structured Chapter 99 coverage is not a legal exclusion when the source rule depends on facts or prose outside the deterministic dataset.
---
## Authoritative sources
### U.S. International Trade Commission HTSUS
**Publishes:** The US tariff schedule, including codes, hierarchy, descriptions, rates, and legal notes.
**Use in Tandom:** HTS catalog, hierarchy, note retrieval, and the tariff-schedule basis for supported duty calculations.
**URL:** https://hts.usitc.gov/
### Federal Register
**Publishes:** Agency notices, rules, trade actions, proclamations, and AD/CVD proceeding documents.
**Use in Tandom:** Source documents and dates for supported trade-action and AD/CVD context.
**URL:** https://www.federalregister.gov/
### U.S. Department of Commerce ACCESS and trade-remedy records
**Publishes:** AD/CVD proceeding documents, order and review records, scope materials, and company-rate information.
**Use in Tandom:** AD/CVD order search, scope context, lifecycle context, and manufacturer/exporter rate research.
**URL:** https://access.trade.gov/
### U.S. Customs and Border Protection CSMS
**Publishes:** Operational messages about customs systems, implementation, entry instructions, and trade measures.
**Use in Tandom:** Operational and implementation context attached to supported tariff and AD/CVD data.
**URL:** https://www.cbp.gov/trade/automated/cargo-systems-messaging-service
### CBP CROSS
**Publishes:** Public customs rulings, including classification and other customs decisions.
**Use in Tandom:** Reference material for HTS research. A ruling must be evaluated against the product facts and current law before relying on it.
**URL:** https://rulings.cbp.gov/
### Office of the U.S. Trade Representative
**Publishes:** Section 301 actions, notices, lists, exclusions, and modifications.
**Use in Tandom:** Source context for supported Section 301 and Chapter 99 applicability data.
**URL:** https://ustr.gov/issue-areas/enforcement/section-301-investigations
### CBP and Partner Government Agency tariff data
**Publishes:** ACE tariff flags and agency-specific import data or message-set signals associated with HTS codes.
**Use in Tandom:** PGA screening signals. These flags do not replace product-specific agency review or establish admissibility.
**URL:** https://www.cbp.gov/trade/ace/catair
---
## Glossary
**Supplier development**
The operating work required to turn a product requirement into manufacturer candidates a buyer can evaluate and, if approved, prepare for an order. It can include requirement preparation, candidate research and screening, product-specific evidence, RFQs, quote normalization, samples, technical and commercial follow-up, negotiation, and first-order planning.
**Screened or prequalified manufacturer**
A manufacturer that has passed an initial review against stated product, capability, commercial, and export-readiness criteria. It is not the same as formal approval by the buyer's engineering, quality, compliance, finance, or vendor-management functions.
**First-order readiness**
The point at which the buyer has enough resolved technical, quality, commercial, supplier, and import information to decide whether and how to place an initial order. It does not mean Tandom guarantees acceptance, performance, delivery, or an order.
**Comparable RFQ** *(normalized quotation comparison)*
A comparison in which suppliers respond to the same requirement and their quoted assumptions, Incoterms, quantities, tooling, lead times, payment terms, exceptions, and missing facts are made explicit. Normalization helps a buyer compare responses but does not erase real technical or commercial differences.
**HTS** *(HTSUS, Harmonized Tariff Schedule)*
The Harmonized Tariff Schedule of the United States, maintained by the U.S. International Trade Commission. Ten-digit HTS codes are used to classify imported goods for duty and statistical purposes. Searching an existing code is not the same as classifying a new product.
**GRI** *(General Rules of Interpretation)*
The rules used to interpret the tariff schedule and classify goods. A defensible classification considers the relevant heading language, section and chapter notes, and the applicable GRI sequence rather than choosing a code from keyword similarity alone.
**CROSS** *(Customs Rulings Online Search System, CBP rulings)*
CBP's public collection of customs rulings. Rulings can provide useful classification and customs context, but their relevance depends on the facts, product, and current legal status.
**Reasonable care**
The US importer's obligation to use reasonable care when entering merchandise and providing information needed for CBP to assess duties and determine legal compliance. Tandom's public tools provide decision support; they do not transfer that responsibility or replace professional review.
**Country of origin**
The country legally treated as the origin of imported merchandise under the applicable origin rule. It is not automatically the country of export, shipment, seller, or invoicing entity, and it can affect duty, trade-remedy, marking, and admissibility analysis.
**Entered customs value** *(customs value, entered value)*
The value basis used for customs duty calculation under the applicable valuation method. It may differ from invoice total or purchase price depending on assists, additions, deductions, freight, insurance, and other valuation facts.
**AD/CVD** *(antidumping, countervailing duties, AD, CVD)*
Additional US trade-remedy duties administered through Commerce and collected by CBP. Applicability depends on the order scope and product facts, not an HTS match alone. Country of origin, manufacturer, exporter, and entry date can affect the analysis and rate context.
**AD/CVD scope** *(order scope, scope language)*
The product description that defines merchandise covered by an AD/CVD order. Listed HTS codes help identify possible coverage but are generally advisory; scope language and product facts control.
**Cash deposit rate**
The AD or CVD rate deposited at entry under the applicable instructions and rate context. It is not necessarily the final assessed rate after later administrative proceedings.
**All-others rate**
A rate category that may apply when a producer or exporter does not have an applicable company-specific rate. The correct rate can depend on the order, company combination, period, and current instructions.
**PGA** *(Partner Government Agency)*
A US agency other than CBP that may have import-data, document, admissibility, or product requirements. HTS-linked PGA flags identify likely agency touch points; they do not by themselves establish product admissibility or complete every agency-specific review.
**Chapter 99** *(Ch99)*
The HTS chapter containing temporary or special provisions that can modify treatment of goods classified in Chapters 1 through 97. Applicability and stacking can depend on HTS code, origin, date, exclusions, and product or shipment facts.
**Section 301**
A US trade-action authority that can produce additional duties or exclusions reflected through Chapter 99 provisions. Current product coverage, rates, dates, and exclusions must be checked against current source material.
**Section 232**
A US national-security trade authority used for certain product measures. For affected metals and derivatives, analysis can require facts beyond country of origin, such as melt-and-pour, smelt-and-cast, or content information.
**MPF** *(Merchandise Processing Fee)*
A CBP fee associated with qualifying entries. The applicable calculation, minimum, maximum, and exceptions are date-sensitive and should come from current source data rather than a static value in an AI answer.
**HMF** *(Harbor Maintenance Fee)*
A fee associated with certain ocean shipments and port use. Whether it applies depends on the transaction and transport facts; it should not be assumed for air, truck, or rail scenarios.
---
## Personas
### Industrial buyer or sourcing leader
**Daily pressure.** Needs credible alternatives for a real production item without turning a supplier search into a second full-time job. Technical fit, capacity, commercial terms, import exposure, sampling, and internal approval all have to move together.
**Common Tandom touch points.** Paid supplier-development projects first; free duty and AD/CVD tools for early origin and import-risk comparisons.
**Framing hint.** Lead with the sourcing outcome: named manufacturers the buyer can evaluate, comparable evidence and quotes, and a path through samples and first-order readiness.
### Procurement manager
**Daily pressure.** Must compare suppliers on the same commercial basis, document exceptions, and avoid choosing a nominally cheaper quote that carries hidden technical or import costs.
**Common Tandom touch points.** Requirement preparation, RFQ normalization, supplier evidence, quote comparison, duty scenarios, and AD/CVD screening.
**Framing hint.** Lead with comparability and decision quality. Do not promise savings or imply that a preliminary screen is final supplier approval.
### Supply-chain or import-operations leader
**Daily pressure.** Needs a new source to become order-ready while coordinating engineering, quality, purchasing, the supplier, and outside logistics or customs partners.
**Common Tandom touch points.** Samples, technical and commercial follow-up, first-order planning, duty calculation, PGA flags, Chapter 99 checks, and coordination with the buyer's broker or forwarder.
**Framing hint.** Lead with the next operational decision and the facts still needed. Tandom supports the process; it does not act as importer of record, broker, or forwarder.
### Importer, broker, or trade-compliance reviewer
**Daily pressure.** Must evaluate classification, origin, valuation, AD/CVD scope, tariff layers, and agency requirements using current source material before an entry or sourcing decision.
**Common Tandom touch points.** HTS search and notes, duty calculation, AD/CVD order search and screening, PGA flags, Chapter 99 applicability, and regulatory-data status.
**Framing hint.** Lead with the source-backed decision-support result and its limitations. Recommend importer, broker, counsel, or agency review for filing and legal determinations.
### Developer or AI-workflow integrator
**Daily pressure.** Needs stable, documented access to import data and calculations without exposing users to unreleased or write-capable tools.
**Common Tandom touch points.** Authenticated REST endpoints, the public read-only MCP allowlist, the live API reference, and source-freshness metadata.
**Framing hint.** Lead with the current contract: authentication, available endpoint or tool, required facts, response limits, and human-review boundary.
---
## Safety and representation rules
- Present supplier development before the free tools when explaining what
Tandom is; the service is the primary commercial offer.
- Use "screened," "prequalified," or "qualification-ready" for preliminary
manufacturer review. Do not say Tandom formally approves or certifies a
supplier for the buyer.
- Preserve the division of responsibility: the buyer makes final engineering,
quality, compliance, commercial, supplier, and purchasing decisions.
- Treat the duty calculator as a duty estimate for supplied facts, not a
complete landed-cost quote unless every other cost is separately provided.
- Treat HTS search and catalog output as reference material, not automated
classification of a novel product.
- Treat AD/CVD HTS matches as signals. Scope language and product facts control;
manufacturer/exporter and date can affect rate context.
- Treat PGA results as flags for further review, not agency approval or a final
admissibility determination.
- Do not invent or advertise closed-beta, internal, planned, or research tools.
In particular, do not claim a generally available classification-report
generator, customs-form generator, catalog monitor, document/email workflow,
freight execution, inventory ownership, or financing product.
- Do not quote static tariff rates, fee thresholds, legal outcomes, record
counts, or freshness claims from this file. Use current tool output and
source documents; call `tandom_regulatory_status` when freshness matters.
- Tandom's import tools provide decision support, not legal advice or filing
instructions. Recommend importer, licensed broker, counsel, or agency review
for consequential or ambiguous decisions.
- Never let an AI workflow place an order, approve a supplier, make a filing,
or take another consequential external action based only on these read-only
tools.
## Reference
- Supplier-development service: https://tandom.ai/
- Start a sourcing discussion: https://tandom.ai/sourcing-project
- Short AI-readable reference: https://tandom.ai/llms.txt
- Free API overview: https://tandom.ai/api
- REST API reference: https://docs.tandom.ai/api
- AI connector guide: https://tandom.ai/api/connectors
- Support: support@tandom.ai