We use cookies.This website uses essential cookies to operate core features. With your consent, we also use analytics cookies to understand traffic and improve the service. For more details, see our .
Was this tool helpful to use?
Your feedback helps us make it better
Look up consumption tax rates by country, state, city, or postal code across 130+ countries and regions.
Overview
Understand what the tool solves, how it works, and the boundaries of its data.
Look up consumption tax rates by country, state, city, or postal code across 130+ countries and regions.
The tool invokes a third-party service through a ToolKK OpenAPI Product and presents the response with human-readable labels. Its main input is a country code plus optional state, city, or postal code; the useful output includes available standard, reduced, combined, and tax-type fields. Use the response for screening, review, and organization rather than triggering an irreversible action from one field alone.
Guide
Follow the workflow and verify inputs and outputs with practical examples.
Content copied from documents or spreadsheets can contain invisible spaces, full-width punctuation, and accidental line breaks. If a request fails, distinguish invalid input from quota limits, timeouts, or temporary provider faults. HTTP 429 and 5xx responses are not proof that the submitted value is invalid.
Use cases
See how the tool fits into real work and everyday tasks.
Typical workflows include cross-border price estimates, checkout guidance, market research, and preliminary finance checks. Adding a structured check before the final workflow can reduce manual entry, repeated research, and inconsistent interpretation. For team use, retain the lookup time, an input summary, returned fields, and the eventual human conclusion.
The result is a point-in-time decision aid. Publishing, payment, user rejection, tax filing, hiring, or content removal should follow documented business rules and preserve a human review or appeal path.
Q&A
Find concise answers to common questions and confusing cases.
The result view prioritizes available standard, reduced, combined, and tax-type fields. Read numbers and Boolean values in context: valid does not mean permanently valid, low risk does not mean impossible, and an empty list does not always prove absence. If repeated results differ, consider the lookup time, provider update cycle, and an authoritative source.
The provider may have no data for that field, or the current plan, region, or input format may not support it. A blank value is not automatically treated as either pass or fail.
No. It is best used for initial screening, organization, and finding items that need human confirmation. Material decisions need business rules and authoritative evidence.
Yes. Every successful call uses the displayed coin price, so avoid repeating an unchanged query without a clear need for refreshed provider data.
Notes
Review scope, result limitations, and important precautions before use.
tax structures differ across 130+ markets, and local surcharges, product classes, or temporary rules may require official verification. Provider databases, model versions, network conditions, free-plan features, and synchronization schedules can also affect the answer. Borderline scores, missing fields, and commercially important records should be retained and verified through an authoritative channel.
provide only the location precision needed for the rate and omit names, street numbers, and full delivery details. Follow data minimization and submit only what the task requires. Protect copied or downloaded results with suitable access controls and retention limits, then delete them when the purpose ends. The page never asks users for an APILayer key; credentials remain in the server-side shared Provider and support multi-key rotation.
Related
Discover related tools, collections, and available API capabilities.