Clear scope. No implied checks.
Understand the website, its fictional examples, and the boundary between documentation and an operational verification service.
What you can do here
Read validation guides, explore five data families, inspect predefined JSON request and response examples, copy those examples, download an illustrative OpenAPI contract, and contact the site by email. The pages and example files are available without an account.
What the website does not do
The website does not verify identity documents, query issuing authorities or postal records, send telephone challenges, verify legal names, issue API keys, or create customer accounts. There is no document-upload or personal-data entry facility.
How to interpret the examples
The example explorer switches between fixed fictional fixtures included with the site. No validation request is made. A value such as structure: pass is part of the illustration; it is not evidence that a real-world check ran. Responses are marked demo: true, and real-world checks remain not_checked.
Route names and response fields are proposed design vocabulary. The OpenAPI download uses a non-operational example hostname. It is not a service contract for a deployed ValidAPI endpoint.
Coverage, pricing, and assurance
No production country coverage, verification-provider relationship, availability guarantee, certification, rate limit, or price is claimed here. References to standards and organizations explain concepts; they do not establish a partnership or endorsement.
Before using a real provider
Review the actual method, authorization, coverage, authentication, processing terms, operational safeguards, and recovery behavior. Apply the production integration checklist to the service you plan to deploy.
Need to clarify a boundary?
Email [email protected] with the page and a high-level question. Do not send real identification documents, credentials, or customer datasets.