vatverify.dev valid
vatverify
REST API for VAT number validation across 32 countries (EU-27, UK, Switzerland, Liechtenstein, Norway). Real checksum algorithms, 30-day caching, and a tax-rules engine.
Their llms.txt
The beginning of the file, from our validated copy saved 2026-10-27T10:04:53.960Z. Cached copy · Source on vatverify.dev
# vatverify
> REST API for VAT number validation across 32 countries (EU-27, UK, Switzerland, Liechtenstein, Norway). Real checksum algorithms, 30-day caching, and a tax-rules engine.
## Documentation
- [Authentication](https://www.vatverify.dev/docs/authentication): API keys, Bearer tokens, and the difference between test-mode and live-mode keys.
- [Caching](https://www.vatverify.dev/docs/caching): 30-day TTL for valid responses, 24-hour TTL for invalid. How to bypass cache when you need a fresh lookup.
- [Introduction](https://www.vatverify.dev/docs): vatverify, the VAT validation API rebuilt for modern stacks. Get started in under 2 minutes.
- [Quickstart](https://www.vatverify.dev/docs/quickstart): Make your first VAT validation request in under 2 minutes.
- [Rate limits](https://www.vatverify.dev/docs/rate-limits): Monthly quotas per plan, what happens at the limit, and how to read X-RateLimit headers.
- [Reliability](https://www.vatverify.dev/docs/reliability): How to handle registry outages. What live, cached, and degraded mean in API responses.
- [Response format](https://www.vatverify.dev/docs/response-format): Every field in the success, error, and batch response envelopes.
- [Supported countries](https://www.vatverify.dev/docs/supported-countries): vatverify validates VAT numbers across 32 countries via 4 official registries: EU-27, UK, Switzerland, Liechtenstein, and Norway.
- [Test mode](https://www.vatverify.dev/docs/test-mode): Use vtv_test_* keys to validate VAT numbers deterministically, perfect for CI, local dev, and end-to-end tests.
- [Webhooks](https://www.vatverify.dev/docs/webhooks): Receive real-time notifications when validations and batch jobs complete, without polling the API.
- [b2c_not_supported](https://www.vatverify.dev/docs/errors/b2c-not-supported): The /decide endpoint only handles B2B transactions. B2C is not supported in v1.
- [batch_too_large](https://www.vatverify.dev/docs/errors/batch-too-large): The vat_numbers array contains more than 50 items.
- [buyer_vat_not_registered](https://www.vatverify.dev/docs/errors/buyer-vat-not-registered): The buyer_vat number passed to /decide is invalid or not registered with the registry.
- [bzst_rejected](https://www.vatverify.dev/docs/errors/bzst-rejected): BZSt returned an unrecognised status code that does not map to a typed vatverify error.
- [bzst_server_error](https://www.vatverify.dev/docs/errors/bzst-server-error): BZSt accepted the request but returned an internal server error (evatr-2004, evatr-2011, evatr-3011).
- [bzst_session_limit](https://www.vatverify.dev/docs/errors/bzst-session-limit): The API hit the per-session quota for qualified confirmations against BZSt (evatr-0008).
- [bzst_unavailable](https://www.vatverify.dev/docs/errors/bzst-unavailable): BZSt is temporarily unreachable or returned a degradation status (evatr-0011, evatr-1001 through evatr-1004).
- [country_unknown](https://www.vatverify.dev/docs/errors/country-unknown): The country code pa
…
Related sites
Similar publisher descriptions and documentation. Similarity does not imply affiliation or equivalent capabilities.
| Domain | Title | Category | Country | Authority | llms.txt | llms-full.txt | Save |
|---|---|---|---|---|---|---|---|
| taxid.dev | TaxID (taxid.dev) | interface APIs and SDKs | US | 46 | ✓ | ✓ | |
| invoicenavigator.eu | Invoice Navigator | interface Finance and payments APIs and SDKs | US | 45 | ✓ | ✓ | |
| numverify.com | Numverify | interface APIs and SDKs | — | 52 | ✓ | ||
| fonoa.com | Fonoa | interface AI and machine learning Finance and payments +1 | IE | 56 | ✓ | ||
| taxually.com | Taxually | documentation Finance and payments Business software | US | 53 | ✓ | ||
| emailvalidation.io | emailvalidation.io | interface APIs and SDKs Communications | — | 51 | ✓ | ✓ | |
| e-invoice.be | e-invoice.be | interface Developer tools APIs and SDKs +1 | BE | 45 | ✓ | ✓ | |
| apivoid.com | APIVoid | interface Cybersecurity APIs and SDKs | US | 59 | ✓ | ✓ |
Machine-readable: GET /v1/resolve?q=vatverify.dev · GET /v1/domain/vatverify.dev · this page as Accept: application/json or text/markdown · MCP lookup_domain
Automatically discovered from public files. Inclusion does not imply endorsement or publisher participation.
Own or manage this website?
If you own or manage vatverify.dev, you can update its listing and review file health, discovery activity and score history.
Manage this listing — optional
What verification unlocks
See how your site is discovered—and control what agents see.
- See your website in the map
Review your indexed topics, nearby publishers sharing headings, measured listing exposure and map snapshots in a private report for your website.
- Control what agents see
Edit your listing description, tags, public contact details and additional llms.txt paths. Publish your terms for automated access, attribution and pricing.
- Make your profile eligible for search
A valid, listed, unblocked, verified profile can appear in our publisher sitemap and become eligible for search-engine visibility. Search engines decide what to index and rank.
- Appear in our llms-full.txt
Eligible verified publishers are listed by name, with their file links and summaries, in the service overview agents can read.
Free. No account registration, backlink or payment required. Public discovery remains available without verification.
Let your coding agent verify it
If your coding agent is authorized to manage this website, paste these instructions into it.
Claim my listing on Agent Web Map for vatverify.dev:
1. POST https://agentwebmap.com/v1/sites/vatverify.dev/claims and keep claim_id and claim_secret private.
2. Publish the verification line "AgentWebMap verification: <token>" (token from step 1) in https://vatverify.dev/llms.txt, or use the DNS, meta-tag or well-known method the response describes. This only verifies the listing; your website and domain remain yours.
3. POST https://agentwebmap.com/v1/sites/vatverify.dev/verify with {"claim_id": "...", "claim_secret": "..."}.
4. Save the api_key from the answer; it manages the listing (PATCH https://agentwebmap.com/v1/sites/vatverify.dev).
MCP equivalent: tools begin_ownership_claim, then verify_domain, at https://agentwebmap.com/mcp. Docs: https://agentwebmap.com/docs#verifyCorrections or removal requests: contact the directory.