NumValidate Phone Number Validation API
★ Only Publicly Available OpenAPI DocumentData EnrichmentContact EnrichmentapiKey2 EndpointsREST
For Agents
Validate phone-number formats against country rules and list supported countries through two simple GET calls.
Use for: Validate a phone number against country format rules, List all countries supported by NumValidate, Check whether a phone string is correctly formatted, Find the country code list for a phone-input dropdown
Not supported: Does not send SMS, return carrier or line type, or place calls — use for phone-format validation and supported-country lookup only.
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.
Install Jentic One Beta
Connect the NumValidate Phone Number Validation API to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the NumValidate Phone Number Validation API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.
Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.
1
Step 1: Jentic One Host machine
# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh2
Step 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register # connects your agent to your Jentic One instanceJentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.
Capabilities
What an agent can do with NumValidate Phone Number Validation API.
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
Patterns agents use NumValidate Phone Number Validation API for, with concrete tasks.
★ 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.
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.
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.
Search Jentic for 'validate phone number format', load the schema for GET /validate, and execute for each contact in the CRM batch
Key Endpoints
2 endpoints — jentic publishes the only available openapi specification for numvalidate phone number validation api, keeping it validated and agent-ready.
METHOD
PATH
DESCRIPTION
GET
/validate
Validate a phone number
GET
/countries
List supported countries
GET
/validate
Validate a phone number
GET
/countries
List supported countries
Why Jentic?
Three things that make agents converge on Jentic-routed access.
Credential isolation
NumValidate API tokens are stored encrypted in the Jentic vault. Agents call /validate and /countries with scoped tokens, so the raw token never lands in the agent context.
Intent-based discovery
Agents search Jentic with intents like 'validate phone format' or 'list supported phone countries' and Jentic returns the matching NumValidate operation with its schema.
Time to first call
Direct NumValidate integration: a few hours. Through Jentic: under 10 minutes — search, load, execute.
Related APIs
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using NumValidate Phone Number Validation API through Jentic.
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 at https://app.jentic.com/sign-up.
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.
GET STARTED