Tariffs API vs Zonos.
Both calculate landed cost. We're built for developers shipping a duty feature this week, not enterprise platform rollouts that take a quarter.
Zonos is a strong choice for cross-border ecommerce brands that want a single vendor for shipping, fraud screening, customs classification, and landed cost. If that's what you're buying, they're a serious option. If all you need is the duty and tariff number for your checkout, this page is for you.
Tariffs API vs Zonos
| Feature | Tariffs API | Zonos |
|---|---|---|
| Pricing | $199/month, public | Per-shipment, contact sales |
| Per Zonos's pricing page (accessed 2026-05-14): "Per shipment fees vary by post and are always visible in your Zonos Dashboard under Billing > Fees." | ||
| Self-serve signup | Yes, 14-day free trial | Account creation available; commercial use typically demo-led |
| API protocol | REST + JSON | GraphQL (REST is legacy per their docs) |
| Time to first call | Under 10 minutes | Demo + onboarding for commercial use |
| Scope | US duty + tariff calculation | Full cross-border suite: Checkout, Landed Cost, Classify, Restrict, Screen, Hello |
| AI agent access | MCP server included | Not listed |
| Stacking coverage | Section 301, 232, IEEPA, Chapter 99 | 200+ country coverage; US-specific stacking detail not published |
When Zonos is the right pick
- →You want an end-to-end cross-border platform — DDP shipping, fraud screening, classification, fulfillment — all under one vendor.
- →You ship into 200+ destinations and want carrier integrations built in.
- →You have budget for a managed solution and a team that can run a demo-led evaluation.
When Tariffs API is the right pick
- ✓You need US duty and tariff calculation at checkout — just the data, fast.
- ✓You want public pricing and self-serve signup, no demo call.
- ✓Your team would rather hit a REST endpoint than integrate a full platform.
- ✓You're building, not buying — and want to ship in days, not quarters.
One endpoint. Deterministic JSON.
GET /api/v1/tariffs/resolve?hts=8541.10.00.80&origin=CN returns the base duty, every applicable Chapter 99 measure, a confidence score, and attempted candidates when the match isn't exact. Bulk endpoint takes up to 200 codes per request. REST + JSON, no SDK required.
GET /api/v1/tariffs/resolve?hts=8541.10.00.80&origin=CN
{
"summary": {
"applicable_ad_valorem_rate": 0.0,
"resolved_additional_ad_valorem_rate": 25.0,
"total_resolved_ad_valorem_rate": 25.0
},
"base_tariff": { "percentage_component": 0.0 },
"additional_measures": [
{
"program": "section_301",
"chapter_99_code": "9903.91.05",
"resolved_rate": { "percentage_component": 0.25 }
}
]
}Switching from Zonos
Can I migrate from Zonos to Tariffs API?
If you're using Zonos only for US duty calculation, yes. The typical migration is one engineering week: replace the Zonos call with GET /api/v1/tariffs/resolve and map the response. If you also use Zonos for shipping, fraud screening, or classification, keep them for those and use Tariffs API just for the duty lookup.
Is Tariffs API cheaper than Zonos?
Zonos doesn't publish pricing, so a head-to-head dollar comparison isn't possible. What we do publish: $199/month flat, 100,000 API calls included, no setup fees, no contract. Cancel any time.
Does Tariffs API replace a customs broker?
No, and neither does Zonos. Both surface duty data; neither files entries or issues binding classifications. For those you need a licensed customs broker.
- Zonos pricing page · accessed 2026-05-14
- Zonos developer documentation · accessed 2026-05-14