Use cases

How teams integrate the Tandom API

Five Ideal Customer Profiles, five concrete integrations. Each card is a runnable code sample using values from our hosted reference. Pick the one that matches your product and copy the call.

Brokerage software / entry-summary workflow

Customs broker

Time to implement: ~1 day

Pain

Calculating the full layered duty stack — MFN base + Section 232 + Section 301 + IEEPA + Reciprocal + AD/CVD + Chapter 99 — for every entry line is error-prone and slows entry-summary turnaround. Rate-table spreadsheets drift out of sync within hours of a new presidential proclamation or FRN.

Integration

Replace the duty-rate spreadsheet with one call. Pass the HTS, origin, declared value, and entry date — receive the layered stack, the effective ad-valorem rate, the citations to the Federal Register / Proclamation / EO, and the Chapter 99 expansions that apply.

Endpoints

GET/v1/duty/calculate

Get a key for this use case →

Sample request

curl https://api.tandom.ai/v1/duty/calculate \
  -H "Authorization: Bearer tk_live_..." \
  -G \
  -d "hts=7307.91.50.10" \
  -d "origin=CN" \
  -d "value=10000" \
  -d "date=2026-04-30"

Response (excerpt)

{
  "dutyInfo": {
    "effectiveRatePercent": 47.5,
    "components": [
      { "type": "MFN", "ratePercent": 5.5 },
      { "type": "Section 301", "ratePercent": 25, "frCitation": "FR 2024-..." },
      { "type": "IEEPA", "ratePercent": 7.5, "executiveOrder": "EO 14256" },
      { "type": "Reciprocal", "ratePercent": 9.5 }
    ],
    "appliedExclusions": [],
    "citations": [...]
  }
}

Quoting workflow / rate request

Freight forwarder

Time to implement: ~2 days

Pain

Quoting a shipment without flagging a likely AD/CVD exposure on the manifest leaves your customer to discover the real landed cost at port — and your team to absorb the operational fallout. Manually scoping every line against every active order doesn't scale.

Integration

Run AD/CVD scope analysis at quote time. Send the manifest description, HTS, and country — get back the matching cases, the company-specific or all-others rate, and a Claude-grounded scope determination with verbatim supporting phrases from the Commerce determination.

Endpoints

POST/v1/adcvd/check

Get a key for this use case →

Sample request

curl https://api.tandom.ai/v1/adcvd/check \
  -H "Authorization: Bearer tk_live_..." \
  -H "Content-Type: application/json" \
  -d '{
    "productDescription": "stainless steel forged flanges, 4 inch, ANSI 150",
    "htsCode": "7307.91.50.10",
    "countryOfOrigin": "CN"
  }'

Response (excerpt)

{
  "matches": [{
    "caseNumber": "A-570-985",
    "scopeAnalysis": {
      "determination": "in_scope",
      "confidence": 94,
      "reasoning": "The product description matches...",
      "supportingPhrases": ["stainless steel forged flanges of any size"]
    },
    "respondentRate": { "rate": 18.42, "rateAppliesTo": "producer" },
    "companionCaseNumber": "C-570-984",
    "combinedRatePercent": 150.82
  }],
  "matchRateRange": { "lo": 18.42, "hi": 150.82 }
}

Line-item entry / product catalog enrichment

ERP vendor

Time to implement: ~1 day

Pain

Customers expect HTS suggestions inside the line-item form, not a tab-out to a separate tool. Maintaining your own HTSUS dataset means tracking every revision the USITC publishes — and reconciling section / chapter notes that scope what your suggestion actually means.

Integration

Type-ahead HTS search backed by the live USITC schedule. Pair with section / chapter notes for the suggestion's regulatory context — embed both in your line-item form so users pick a code and see the constraints in one view.

Endpoints

GET/v1/hts/search
GET/v1/hts/notes

Get a key for this use case →

Sample request

# 1. Type-ahead search
curl https://api.tandom.ai/v1/hts/search \
  -H "Authorization: Bearer tk_live_..." \
  -G -d "q=stainless+steel+flanges"

# 2. Show section / chapter notes for the picked code
curl https://api.tandom.ai/v1/hts/notes \
  -H "Authorization: Bearer tk_live_..." \
  -G -d "htsCode=7307.91.50.10"

Response (excerpt)

{
  "query": "stainless steel flanges",
  "count": 12,
  "results": [{
    "htsno": "7307.91.50.10",
    "description": "Flanges, stainless steel, forged",
    "general": "5.5%",
    "units": ["kg"],
    "chapter": "73"
  }]
}

Landed-cost engine / Section 301 awareness

Logistics SaaS

Time to implement: ~2 days

Pain

Section 301 List 1–4 + the rolling Chapter 99 additions on top of every product origin make landed-cost engines unmaintainable in code. Hardcoding rates becomes a quarterly emergency every time a new tranche or exclusion drops.

Integration

Resolve Chapter 99 applicability per HTS + country, then expand the Section 301 scope to surface the specific subheadings, exclusions, and effective dates that apply. Surface the Federal Register citation alongside every rate so your customers can audit.

Endpoints

GET/v1/chapter99/applicable
GET/v1/hts/expand-s301

Get a key for this use case →

Sample request

# 1. Chapter 99 additions for an HTS + origin pair
curl https://api.tandom.ai/v1/chapter99/applicable \
  -H "Authorization: Bearer tk_live_..." \
  -G \
  -d "htsCode=8471.30.01.00" \
  -d "origin=CN" \
  -d "date=2026-04-30"

# 2. S301 scope expansion (which subheadings + exclusions)
curl https://api.tandom.ai/v1/hts/expand-s301 \
  -H "Authorization: Bearer tk_live_..." \
  -G -d "htsCode=8471.30.01.00"

Response (excerpt)

{
  "applicable": [
    {
      "ch99Code": "9903.88.01",
      "tariffPercent": 25,
      "tranche": "List 1",
      "frCitation": "83 FR 28710",
      "effectiveDate": "2018-07-06"
    }
  ]
}

AD/CVD lifecycle monitoring / scope-drift research

In-house compliance team

Time to implement: ~1-2 days

Pain

Tracking every administrative review, sunset, scope ruling, and circumvention inquiry across the cases that touch your product mix is a full-time research role. Missing one means importing under the wrong rate or missing a window to comment.

Integration

Pull the full lifecycle for each active case in your mix — scheduled reviews, sunset windows, scope rulings filed, court decisions issued. Cron the pull and diff against your last snapshot to surface changes in your own systems.

Endpoints

GET/v1/adcvd/orders
GET/v1/adcvd/lifecycle

Get a key for this use case →

Sample request

# 1. Orders matching the cases in your product mix
curl https://api.tandom.ai/v1/adcvd/orders \
  -H "Authorization: Bearer tk_live_..." \
  -G -d "country=CN" -d "product=flanges"

# 2. Full lifecycle (reviews, sunsets, scope rulings, CIT)
curl "https://api.tandom.ai/v1/adcvd/lifecycle?caseNumber=A-570-985" \
  -H "Authorization: Bearer tk_live_..."

Response (excerpt)

{
  "caseNumber": "A-570-985",
  "lifecycle": {
    "reviewsScheduled": [
      { "type": "administrative_review", "periodOfReview": "2025-2026", "estimatedFrCitation": "FR 2026-..." }
    ],
    "sunset": { "nextReviewDue": "2028-08-14" },
    "scopeRulings": [{ "rulingDate": "2024-06-01", "outcome": "in_scope" }],
    "citDecisions": []
  }
}

Don't see your integration?

These five aren't the only shapes — anywhere in trade-compliance software where rates, scope, classification, or PGA flags are decided is a place this API plugs in. Browse the full reference at docs.tandom.ai/api or import the Postman collection and explore.

AI agents and LLM dev tools — start at docs.tandom.ai/llms.txt.