API COVERAGE

See what the APIs actually know.

One transparent view of the Cleo Legal Data corpus and the Customs Classification engine: jurisdictions, source registry, endpoint scope and known gaps.

Registry sources
1,479
all statuses
Jurisdictions
177
country + bloc profiles
Complete sources
658
44% of registry
Live documents
2,008,008
99% health
02 · CUSTOMS CLASSIFICATION API

Product description in. Ranked customs candidates out.

The classifier accepts a product description, optional destination country and a nomenclature system. It returns candidate codes, confidence, ambiguity and rationale. Classification is advisory: the response is not a binding customs ruling.

HS6

Available

Global harmonised-system level matching used as the common base.

CN8

Available

EU Combined Nomenclature / TARIC schedule coverage.

TN VED

Available

EAEU schedule coverage for BY, KZ, RU, AM and KG.

HTS

Available with qualification

US tariff route is supported; confirm the returned system and resolution before filing.

Coverage that is safe to sell

  • National / union schedules: EU, GB, US and the five EAEU member schedules are documented in the current tariff handoff.
  • Bloc resolution: six GCC states may resolve through a labelled bloc approximation; this is not the same as a national tariff line.
  • Known gaps: no national tariff line is documented for India, Indonesia, Malaysia, Egypt, Philippines, Nepal, Nigeria, Kenya, Tanzania or Uganda in the current corridor snapshot.

The API returns coverage_status: not_seeded when a route works but the requested code / country pair has no seeded row.

Customs endpoints

GET/v2/customs/lookupDescription → ranked HS / CN / TN VED / HTS candidates.
GET/v2/customs/dutiesDuty, VAT, excise and provenance for a code + destination.
GET/v2/customs/obligationsLegally required and contractually expected obligations.
POST/v2/customs/landed-costCIF + duty + tax stack with explicit partial-data flags.
GET/v2/customs/dual-use-checkPreliminary control screening; not a binding ruling.
POST/v2/compliance/checkComposite classification + selected customs checks.
Important: duties and landed-cost responses carry provenance, confidence and completeness fields. A missing rate is not a zero rate; render the API’s disclaimer and route uncertain classifications to a customs professional.
START WITH EVIDENCE

Browse the source registry, then make the first API call.

Verified: 4/7 static numeric claims checked against source · 0 estimates · 3 live-health claims intentionally not hardcoded. Registry figures read from public/data/manifest.json; live corpus figures are rendered only after a successful GET /health. Customs scope and limitations read from the API repository’s current route contract and corridor coverage handoff. No market-size or completeness claim is inferred from these figures.