About Veriport

Who maintains it

The maintainer is the managing member of the publisher, who writes the code, reads the national pages at each monthly review, answers support and signs the changelog. The name is shown here from the company record (see the box below) so that the publisher behind every page is a person as well as a company.

How the service is run

Three rules, in force since the first release. Every fact the API states points at a dated source: the rates rows name the pages they were read from and the day; a VIES answer says whether it was live or cached and when; a registry record says which registry answered and when. Nothing is counted when you got no answer: a 4xx, a 5xx or a structural refusal costs no call. Breaking changes do not happen inside v1: additive changes ship and appear in the changelog; a v2 would come with a notice period.

Availability is published, not promised: the status page shows the components and the live availability of VIES per member state; the monthly plan is sold under a fair-use rule and that public record. Prices include the tax of your country, charged by Stripe; refunds follow the rule on the pricing page.

What it will not claim

That a valid VAT number proves who your customer is. That a well-formed IBAN proves the account exists or belongs to your payee. That a category hint is the legal classification of your supply. That the rates table is the law: it is a dated transcription of the official pages, reviewed monthly, and the sources are linked so that you can read them on the day.

Where else to find it

The OpenAPI document at /openapi.json is the contract. The SDKs for TypeScript and Python, the MCP server, the Postman collection and the directory listings are published by the maintainer under the same name; the table says which exist today (those are the sameAs of the Organization record of this site) and which are prepared in the repository and not yet published. Nothing is claimed that does not exist.