Free EU VAT Validation APIs: Honest Comparison of Limits and Trade-offs

'Free' means different things across EU VAT validation APIs. Some impose very low request limits. Some restrict HTTPS to paid plans. Some are free indefinitely for low volume but have no path to production scale. And one option — calling VIES directly — is technically free but comes with enough operational complexity that the real cost is developer time, not money. This guide compares every genuinely free EU VAT validation option in 2026, including the trade-offs that are not always obvious from the pricing page.

The Options at a Glance

TaxID: 100 req/month, HTTPS, Full Feature Set

TaxID offers 100 validations per month on the free tier with no credit card required. The free tier includes HTTPS, returns company name and address when available, provides explicit VIES downtime status codes (service_unavailable), and has the same API interface as paid tiers — no feature degradation for free users. The 100-request limit resets monthly and does not roll over.

For context, 100 requests per month is enough for: validating 3-4 new B2B customers per working day during development, running a closed beta with 20-30 users plus re-validations, or handling a low-volume internal tool. It is not enough for a production SaaS with more than 50-100 B2B signups per month. The upgrade to the Starter plan ($19/month, 10,000 requests) is the clear path once you exceed the free tier — no custom pricing, no sales call.

TaxID's free tier is a genuine 'try the full product' experience rather than a crippled sample. The same API key, endpoint, and response format work on free and paid tiers. If you build your integration on the free tier, upgrading requires only a payment method — no code changes.

VatCheckAPI: 500 req/month Free Tier

VatCheckAPI offers 500 requests per month on its free tier — the most generous by raw volume among the API-based options. It includes HTTPS, returns company name where available, and covers all 27 EU member states. The 500-request limit makes it suitable for a small production deployment: a SaaS with up to 50 B2B customers per month (assuming 10 validation touches per customer including re-validations) could operate on the free tier indefinitely.

The trade-offs: VatCheckAPI's paid plan caps at 5,000 validations per month before requiring custom pricing. If you need more than 5,000/month, you hit the same custom-pricing wall that Vatstack has. The error handling documentation is less detailed than TaxID's — VIES downtime is surfaced as a generic error rather than an explicit service_unavailable status code, which makes resilience logic harder to implement correctly. For a small internal tool or low-volume B2B application, the 500 free requests are a genuine advantage.

Vatstack: 20 req/month — Tight for Development

Vatstack's free tier is 20 validations per month. That is one API call per working day, which runs out quickly during active development. It is adequate for testing a single integration path (does the request format work, does the response parse correctly) but not for running a prototype, testing error handling scenarios, or demoing the feature to your team. You will upgrade before you are done building.

Vatstack's paid tier starts at $9/month for 1,000 validations — the lowest entry price among the API options. If your use case is genuinely low volume (under 1,000 validations per month) and you need Vatstack's specific features (webhooks, team dashboard), the $9 entry price is a reasonable starting point. But the 1,000/month ceiling on the paid plan means you will hit custom pricing quickly if your product grows. See the Vatstack vs TaxID comparison for the full analysis.

Vatlayer: HTTP-Only Free Tier

Vatlayer offers 100 requests per month on its free tier — matching TaxID on volume. The critical limitation: the free tier only supports HTTP, not HTTPS. In 2026, HTTP-only API access is functionally unusable for any production application. Your API key is transmitted in plaintext over HTTP requests, making it trivially interceptable on any network between your server and Vatlayer's endpoint. HTTPS is available on Vatlayer's paid tiers starting at $9.99/month.

This matters for development too, not just production. Modern development environments default to HTTPS-only security policies, and many reverse proxies and deployment platforms (Vercel, Render, Fly.io) reject outbound HTTP calls from application code by default. You can work around this in development with configuration changes, but it is operational friction that does not exist with any other option on this list. We recommend against Vatlayer's free tier for new integrations specifically because of the HTTP limitation.

Calling VIES Directly: Free but Expensive in Time

VIES is operated by the European Commission and is accessible directly at no cost, with no request limits. If you need unlimited validations without a per-request cost, VIES direct is technically an option. The practical challenges: VIES uses SOAP/XML (not REST/JSON), requires a SOAP client library, has no caching infrastructure (every request is a live round-trip), has no normalised error codes for downtime handling, returns error messages in the language of the target member state's system, and goes offline for maintenance regularly with no programmatic status endpoint.

Building a production-grade EU VAT validation system on raw VIES requires implementing format validation for all 27 countries, a SOAP client, a caching layer, retry logic with exponential backoff, timeout handling, normalised error codes, and monitoring. The development time for this infrastructure, even at a conservative estimate of 3-5 engineering days, exceeds the cost of a year of TaxID's Starter plan. VIES direct makes sense for research, one-off scripts, or compliance audits where you need to verify the upstream source — it does not make sense as the foundation for a production validation system.

What to Look for Beyond the Free Tier

The free tier comparison is the starting point, not the decision criterion. Before choosing a provider, evaluate these factors that only matter once you are in production:

• →Explicit VIES downtime handling: does the API return a distinguishable status when VIES is unavailable, or does it return a generic error? Distinguishable status (service_unavailable) is essential for correct checkout logic. See VIES Downtime: How to Build a Resilient Flow.
• →Response caching: does the API cache validated results? For synchronous checkout validation, the difference between 10ms (cached) and 500ms (uncached VIES call) is visible to users.
• →Scale path: what does validation cost at 10,000, 100,000, and 1,000,000 requests per month? Is it on a public pricing page or does it require a sales conversation?
• →Format validation before quota: does the API consume your monthly request quota on malformed numbers? A well-designed API validates format locally and only counts VIES round-trips against quota.
• →Migration cost: how hard is it to switch providers? An API with standard REST conventions and clear response schemas is easy to swap out. A proprietary SDK or unusual authentication scheme increases lock-in.
• →SLA and uptime: what does the provider guarantee? A service with no published SLA is acceptable for development but not for production checkouts.

The Hidden Cost of 'Free' VIES Calls

When evaluating free tier options, factor in the operational cost of each additional request beyond the free tier. For TaxID, the path from free (100/month) to the next tier (10,000/month, $19) is a simple self-service upgrade. For Vatlayer, the path from free (100/month, HTTP only) to the first paid tier (100/month, HTTPS included) requires entering payment details to get HTTPS — you are essentially paying to remove a security limitation. The practical free-tier value of Vatlayer is therefore near zero for production use.

The comparison also looks different when you factor in error handling and developer time. If you spend two hours debugging why your integration intermittently fails because VIES is down and the API returns a generic error with no distinguishable downtime status, the developer time cost exceeds any monthly API fee. An API with explicit service_unavailable handling saves hours of debugging and reduces production incidents. Factor this into the TCO comparison alongside the per-request price.

For teams starting with a free tier and expecting to upgrade within 6-12 months, choose the provider whose paid tiers are public and predictable. Spending 3 months on a Vatstack integration only to discover that upgrading beyond 1,000/month requires a sales conversation adds time and uncertainty to your growth planning. TaxID's entire public pricing ladder (free through 1,000,000/month) is on one page with no sales gate.

Choosing the Right Free Tier for Your Use Case

For building and testing a new integration: TaxID or VatCheckAPI. Both offer HTTPS on the free tier and enough requests to build and verify a complete integration including error handling for all status codes. TaxID's explicit service_unavailable handling is particularly valuable during development — you can test your downtime logic without simulating infrastructure failures.

For a low-volume internal tool you intend to keep on the free tier permanently: VatCheckAPI's 500/month free tier has the most headroom. If your internal application validates fewer than 500 numbers per month (a team of 5 using a tool to check suppliers, for example), VatCheckAPI's free tier may cover you indefinitely. Verify the provider's reliability and response to downtime before committing to a zero-cost long-term dependency.

For prototyping before committing to a paid plan: both TaxID and VatCheckAPI are suitable. Avoid Vatlayer for prototyping because the HTTP-only limitation creates friction that is not representative of the production experience you would have on a paid tier. The free tier should prototype the same experience as the paid product — Vatlayer's does not.

API Key Security on Free Tiers

On free tiers, API key security is just as important as on paid plans. Your free-tier API key has the same authentication authority as a paid-tier key — anyone with access to your key can use your quota (and cause you to hit your free tier limit unexpectedly) or make validation calls that appear in your audit logs. Never expose your API key in client-side JavaScript, public GitHub repositories, or environment variables committed to version control.

A common mistake with free-tier integrations is building quickly and committing the .env file to a repository. Even if you later remove it, the key is in your git history and needs to be rotated. Set up a .gitignore for .env files before writing a single line of integration code. Store API keys in your CI/CD platform's secret management (GitHub Actions secrets, Vercel environment variables, AWS Secrets Manager) rather than in files on disk. Rotate your key if you have any reason to believe it may have been exposed — TaxID key rotation is available from the dashboard.

For development environments shared between multiple developers (for example, a shared staging environment or a development VM), avoid putting a single shared API key in the environment configuration. Each developer should use their own TaxID account and API key for development purposes. This keeps development usage separate from production usage, prevents one developer's testing from exhausting the team's production quota, and makes it easier to audit who made which validation calls during debugging.

Upgrading from Free to Paid: What Changes and What Does Not

When you upgrade from a free tier to a paid plan, the API endpoint, authentication method, response format, and error codes are identical. There are no code changes required. The only difference is the monthly quota and the billing details on your account. This is by design — the free tier is a full-feature trial of the production API, not a crippled version. You test exactly the code that will run in production.

The upgrade process for TaxID is self-service: add a payment method to your account and select a plan. No sales call, no contract review, no onboarding meeting. The new quota is available immediately after upgrading. If you need to upgrade mid-month because you hit your free tier limit earlier than expected, the new quota applies from the moment you upgrade — you do not need to wait until the start of the next month. This is particularly useful for teams running a marketing campaign or onboarding push that drives more B2B signups than anticipated.

The right free tier for your use case depends on your development timeline and expected production volume. Use TaxID for new integrations where you want a complete developer experience from day one and a clear upgrade path to scale.