TariffsAPI and TariffTrust answer the same question for the same market: what goods imported into the United States will owe, from the base rate to the additional duties of Chapter 99. Both publish their prices, cite the Chapter 99 measure behind a duty, take a date other than today and offer an MCP server. The differences are in the clients, the prices, what an answer carries and what each does when it cannot establish a duty.
Side by side
| TariffTrust | TariffsAPI | |
|---|---|---|
| Made for | Importers, customs brokers and developers, for goods imported into the United States. | “The US duty and tariff API for landed cost”, for importers, customs brokers and supply-chain platforms. |
| Free use | The calculator and the HTS explorer, without an account. | A free calculator without a card; an email is asked for the line-by-line detail. A 14-day API trial, card required. |
| Published prices | Free calculator; Essentials $49/month (5,000 estimates a month), Pro $99/month (10,000 estimates and API requests a month); yearly prices offered. | Starter $99/month (1,000 calls), Developer $199/month (10,000 calls), Enterprise on request; yearly prices offered. |
| Countries | US imports only, from any country of origin. | US imports only, from 249 origin countries. |
| US additional duties it names | Sections 301, 232, 201 and 338, and column 2 rates; antidumping and countervailing duties are excluded. | Sections 301, 232, 201 and 338; the IEEPA tariffs and the Section 122 surcharge, which have ended, at a date in their period. |
| The source of each duty | Each duty with its Chapter 99 heading and a link to its official source. | Each calculation cites the HTS subheading, the Chapter 99 measure and the CBP CSMS message. |
| Product classification | No: it suggests the lines of the tariff whose description matches, and the choice of code stays yours or your broker's. | No: a keyword search of the tariff. |
| API | REST, with a Bearer key: a product, a batch, a whole declaration, a product's history. | REST and JSON, with a Bearer or X-API-Key header; batches of 200 codes. |
| Official clients | Python and Node.js, typed, with safe retries. | None stated; examples in JavaScript, Python, Ruby, PHP and cURL. |
| MCP server for AI agents | Yes, with every plan that includes the API. | Yes, on the Developer and Enterprise plans. |
| Entry fees (MPF, HMF) | Yes, counted once per declaration. | Added by the calculator; not mentioned in the API documentation. |
| Other dates than today | Past dates (as_of) and the duties of a product over a period, from September 28, 2026. | An as_of date on its main operations. |
TariffsAPI's column says what its own public pages state, as read on November 15, 2026; "Not stated" means its pages do not say. Offers change: if something here is out of date, write to contact@tarifftrust.com and we will correct it.
Where TariffsAPI does more
- Its documentation gives examples in more languages, Ruby and PHP among them.
- It returns the measures that have ended, the IEEPA tariffs and the Section 122 surcharge, for an
as_ofdate in the period they were in force; TariffTrust answers for dates from September 28, 2026. - It lets an API key be sent in an
X-API-Keyheader as well as a Bearer token.
Where TariffTrust does more
- Official clients. Typed Python and Node.js packages, with safe retries counted once in the quota; TariffsAPI states none.
- The MCP server from $99 a month, with the Pro plan, where TariffsAPI's comes with its Developer plan, at $199 a month.
- The entry fees in the API, counted once per declaration of several products, as on a real entry.
- Unknown is never zero. When a duty depends on a detail of the goods, the answer says which question changes it, takes the ordinary case and names it, or gives no total rather than a wrong one.
- A free calculator without an email, every line explained with its source.
Which one to choose
Both serve a developer who needs US duties in code. Compare the prices of the plans for your volume of calls, and try both on your own codes: the free calculators show what each answers, line by line.