canonical: https://jentic.com/apis/numvalidate.com/numvalidate # NumValidate Phone Number Validation API Jentic publishes the only available OpenAPI specification for NumValidate Phone Number Validation API, keeping it validated and agent-ready. NumValidate is a free phone-number validation REST API that confirms whether a number is correctly formatted for a given country and returns the list of supported countries. The API exposes two GET endpoints: one to validate a phone string and one to enumerate supported countries for client-side selection. It is a lightweight choice for hobby projects, internal tools, and lead-form filtering where deep carrier data is not required. ## For AI agents Validate phone-number formats against country rules and list supported countries through two simple GET calls. ## Scope Does not send SMS, return carrier or line type, or place calls - use for phone-format validation and supported-country lookup only. ## Capabilities - Validate the format of a phone number for a given country - List every country supported by the validator - Filter form submissions for malformed phone numbers - Confirm international dialling format before storing a contact - Power a country picker on a registration form ## Use cases ### Lightweight Form Validation Indie apps and side projects validate phone-number format at signup by calling GET /validate before persisting the contact. NumValidate's free tier and minimal surface area make it appealing when carrier-level enrichment is unnecessary. The /countries endpoint feeds a country-picker on the same form. Example prompt: Call GET /validate with the user's phone number, reject the signup if the response indicates an invalid format ### Country Picker Population Front-end forms call GET /countries on first load to populate a country selector with the exact list NumValidate supports. Pairing the picker with the validator means the user never picks a country the API cannot handle, eliminating a class of validation errors. Example prompt: Call GET /countries, render a dropdown with the returned list, and use selected country alongside GET /validate ### Agent-Driven Phone Hygiene An AI agent cleaning a CRM iterates over contact records and validates phone format through Jentic. Records that fail validation are flagged for human review. The agent searches Jentic, loads GET /validate, and processes records in a loop without writing any HTTP boilerplate. Example prompt: Search Jentic for 'validate phone number format', load the schema for GET /validate, and execute for each contact in the CRM batch ## Key endpoints | Method | Path | Description | | --- | --- | --- | | GET | `/validate` | Validate a phone number | | GET | `/countries` | List supported countries | ## Key resources - **Validation** — Validate the format of a phone number - **Countries** — List supported countries for validation ## Why Jentic - **Setup:** Wiring NumValidate by hand means setting up its x-api-token header auth and handling the request wiring against numvalidate.com/api yourself. Through Jentic you install once, import NumValidate from the API Directory, store the token once, and your agent calls it. - **Permission scoping:** NumValidate carries no resource id in its paths, so scope the agent to the operations it needs: you can allow the phone format validation and supported-country lookup and leave everything else out. You choose the operations it may call, so it only reaches the endpoints you list. - **Credential handling:** Your NumValidate token is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context. - **Discovery method:** Agents search Jentic by intent such as 'validate phone format' or 'list supported phone countries', and Jentic returns the matching NumValidate operation with its input schema so the agent calls the right endpoint without browsing the reference docs. ## Related APIs - **NumLookupAPI** — Phone validation with carrier and line-type metadata across 230+ countries - **numverify** — Phone validation with carrier and country detail via apilayer - **Abstract API** — Validation suite covering phones, emails, IPs, and more in one product ## FAQ ### Why is there no official OpenAPI spec for NumValidate? NumValidate does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call NumValidate Phone Number Validation API via structured tooling. It is validated against the live API and kept up to date. Get started with Jentic One, the self-hosted execution layer. ### What authentication does NumValidate use? The spec declares an apiToken apiKey scheme. Through Jentic the token is stored encrypted in the vault and injected at execution time, so it never enters the agent's context. ### Can I see which countries NumValidate supports? Yes. Call GET /countries to retrieve the full list of supported countries. Use the response to populate a country picker on your form so users only choose values the validator can handle. ### How do I validate a phone number through Jentic? Search Jentic for 'validate phone number format', load the schema for GET /validate, and execute with the phone number string. Jentic returns the parsed validation result without you needing to handle the auth header directly. ### Does NumValidate return carrier or line type information? No. NumValidate focuses on format validation and returns whether the number parses correctly for its country. If the agent needs carrier or line type, use a richer service such as NumLookupAPI or Twilio Lookup instead. ### What are the rate limits for NumValidate? The OpenAPI spec does not declare explicit rate limits. NumValidate applies free-tier limits per token in production; check the dashboard at numvalidate.com to confirm the quota for your account. ### Can I limit what my agent is allowed to do with the NumValidate Phone Number Validation API? Yes. NumValidate has no resource id in its paths, so with your self-hosted Jentic One you scope the agent by choosing which operations it may call. You can allow only phone-format validation (GET /validate) and supported-country lookup (GET /countries), or grant just one of them, and the agent can never reach an endpoint you did not list. Your own rules and your stored API token decide exactly what the agent is permitted to do.