MobileValidate provides a comprehensive phone and email verification API designed to help businesses prevent fraud, improve deliverability, and enhance user onboarding. The service offers carrier lookups, HLR checks, spam reputation, MNP data, and email mailbox existence verification, supporting integration with messaging apps and consumer platforms.
mobilevalidate-com publishes 7 API contracts indexed on the APIs.io network, including Account API, Catalog API, Jobs API, and 4 more. Tagged areas include Fraud Prevention, Phone Validation, Email Verification, API Service, and Telecommunications.
The mobilevalidate-com catalog on APIs.io includes 1 event-driven AsyncAPI specification, 1 JSON-LD context, and 1 Spectral governance ruleset.
mobilevalidate-com’s developer surface includes CLI, changelog, authentication, engineering blog, documentation, API reference, pricing, and 37 more developer resources.
Regulatory Posture applies to this provider. Its tags matched the
Telecommunications regime, so
Regulatory Posture carries 15 points of the composite.
If this regime is wrong for your business, say so on your
provider repo — the
applicability map is public and we will correct it.
Create-or-Update Ergonomics applies to this provider. This API accepts writes, so it
carries 10 points of the composite. It is scored from the published contracts
themselves: whether a caller can create-or-update in one call, whether the write accepts a key the caller already
holds, and whether the response says which branch ran. Without that, every write needs a search-and-branch in
front of it, and the first time that check is skipped a duplicate record is created.
Scored against the observed mean rather than raw — a provider at the catalog average is unchanged by this facet,
not penalised by it.
The six quality facets above are damped to 75 points between them,
because the conditional facet above carries the other
25. That is why each facet's contribution is shown against a damped
maximum: raising a quality facet moves the composite by 75% of its nominal
weight, not 100%. The full arithmetic is at apis.io/rating/.
Show this score on your site.
It updates itself when the score changes. Paste this where you link to your API docs:
<a href="https://apis.io/providers/mobilevalidate-com/"><img src="https://apis.io/badge/mobilevalidate-com/card.svg" alt="mobilevalidate-com on APIs.io — Kin Score by API Evangelist"></a>
Other styles, a README pill and a shields.io endpoint are on the badge page.
Raise your score.
Agent readiness — checks not met, largest first (exact, from this profile):
MCP Server+12 pts — deployment.mode + probe verdict on the mcp/ manifest, not the pointer; an unprobed slug falls back to authorship Ask about this →
Delegated User Identity+6 pts — a served discovery document listing authorization_code in grant_types_supported (served), else an oauth2 authorizationCode flow or openIdConnect declared in an OpenAPI (documented) Ask about this →
Protected Resource Metadata+5 pts — a served /.well-known/oauth-protected-resource carrying `resource` (documented), and naming its authorization_servers (verified) Ask about this →
3 more unmet checks in the Agent Readiness table above.
Kin Score — facets with the most composite points still available (weight × headroom):
Each check links to what satisfies it. Publish the artifact, or tell us where it already lives, and the score moves on the next scoring run.
Not sure how this applies to your stack? Ask about any one item. Kin Lane reads every question, looks at your profile and your situation, and replies with what a fix would take — scoped to that one area, priced up front, yours whether you ship it or not. Ask a question →
Standards this provider implements or carries. De facto ones are profiled and measured by the API Commons; formal ones come from the standards directory and are linked by the provider's own tags. The evidence column says how each claim was established — not that it was made.
Service catalog (GET /v1/services is authoritative at run time). **Spam reputation (`number.spam`, alias `spam`).** Whether a phone number appears in spam and nuisance-call repo...
Signed notifications (Standard Webhooks) when lookups and jobs finish. See the `webhooks` section for the event payloads and https://mobilevalidate.com/docs/webhooks for signatu...
aid: mobilevalidate-com
name: mobilevalidate-com
accessModel:
pricing: unknown
onboarding: unknown
trial: false
try_now: false
public: false
label: Unknown
confidence: low
source:
- authentication
- security
generated: '2026-11-13'
method: derived
image: https://mobilevalidate.com/media/og/know-before-you-send-light.jpg
description: MobileValidate provides a comprehensive phone and email verification API designed to help businesses prevent
fraud, improve deliverability, and enhance user onboarding. The service offers carrier lookups, HLR checks, spam reputation,
MNP data, and email mailbox existence verification, supporting integration with messaging apps and consumer platforms.
url: https://artifacts.apis.io/mobilevalidate-com/apis.yml
x-type: company
x-source: harvest:mcp-registry
x-tier: profiled
x-tier-reason: enrichment pass 2026-10-31 (modular-v1; was harvest)
specificationVersion: '0.20'
created: '2026-10-30'
modified: '2026-10-30'
tags:
- Fraud Prevention
- Phone Validation
- Email Verification
- API Service
- Telecommunications
tags_raw:
- Fraud Prevention
- Phone Validation
- Email Validation
- API Service
- Telecom
maintainers:
- FN: Kin Lane
email: kin@apievangelist.com
- FN: APIs.json
email: info@apis.io
common:
- type: AgenticAccess
url: agentic-access/mobilevalidate-com-agentic-access.yml
- type: Spectral
url: rules/mobilevalidate-com-rules.yml
- type: JSONLD
url: json-ld/mobilevalidate-com-context.jsonld
- type: Vocabulary
url: vocabulary/mobilevalidate-com-vocabulary.yml
- type: AgentSkill
url: skills/_index.yml
- type: Webhooks
url: asyncapi/mobilevalidate-com-webhooks.yml
- type: DataModel
url: data-model/mobilevalidate-com-data-model.yml
- type: CLI
url: cli/mobilevalidate-com-cli.yml
- type: ChangeLog
url: changelog/mobilevalidate-com-changelog.yml
- type: Idempotency
url: conventions/mobilevalidate-com-conventions.yml
- type: Conventions
url: conventions/mobilevalidate-com-conventions.yml
- type: Security
url: https://mobilevalidate.com/trust
- type: Authentication
url: authentication/mobilevalidate-com-authentication.yml
- type: Deprecation
url: https://mobilevalidate.com/docs/versioning.md
- type: Lifecycle
url: lifecycle/mobilevalidate-com-lifecycle.yml
- type: ErrorCatalog
url: errors/mobilevalidate-com-problem-types.yml
- type: Conformance
url: conformance/mobilevalidate-com-conformance.yml
- type: LLMsTxt
url: llms/mobilevalidate-com-llms.txt
- type: SecurityTxt
url: well-known/mobilevalidate-com-security.txt
- type: WellKnown
url: well-known/mobilevalidate-com-well-known.yml
- type: Hosts
url: hosts/mobilevalidate-com-hosts.yml
- type: Vendors
url: vendors/mobilevalidate-com-vendors.yml
- type: TrustCenter
url: https://mobilevalidate.com/trust
- type: TermsOfService
url: https://mobilevalidate.com/legal/terms
- type: StatusPage
url: https://mobilevalidate.com/status
- type: PrivacyPolicy
url: https://mobilevalidate.com/legal/privacy
- type: Login
url: https://app.mobilevalidate.com/login
- type: DeveloperPortal
url: https://mobilevalidate.com/blog/category/developers
- type: ChangeLog
url: https://mobilevalidate.com/changelog
- type: Blog
url: https://mobilevalidate.com/blog
- type: VulnerabilityDisclosure
url: security/mobilevalidate-com-vulnerability-disclosure.yml
- type: DomainSecurity
url: security/mobilevalidate-com-domain-security.yml
- type: Website
url: https://mobilevalidate.com/
- type: Documentation
url: https://mobilevalidate.com/docs
- type: APIReference
url: https://mobilevalidate.com/docs
- type: Pricing
url: https://mobilevalidate.com/pricing
- type: GettingStarted
url: https://mobilevalidate.com/docs
- type: Support
url: https://mobilevalidate.com/contact
- type: UsageTerms
url: terms/mobilevalidate-com-terms-of-service.yml
- type: DataProcessing
url: privacy/mobilevalidate-com-privacy-policy.yml
- type: DeprecationSchedule
url: deprecation/mobilevalidate-com-deprecation-policy.yml
- type: Eligibility
url: eligibility/mobilevalidate-com-eligibility.yml
- type: AIPreferences
url: ai-preferences/mobilevalidate-com-ai-preferences.yml
- type: DataLicense
url: data-license/mobilevalidate-com-data-license.yml
apis:
- aid: mobilevalidate-com:mobilevalidate-com-account-api
name: mobilevalidate-com Account API
description: Balance, limits and usage of the key's account.
humanURL: https://mobilevalidate.com/docs
baseURL: https://api.mobilevalidate.com/v1
tags:
- Account
tags_raw:
- account
properties:
- type: OpenAPI
url: openapi/mobilevalidate-com-account-api-openapi.yml
- type: JSONSchema
url: json-schema/mobilevalidate-com-money-schema.json
- aid: mobilevalidate-com:mobilevalidate-com-catalog-api
name: mobilevalidate-com Catalog API
description: 'Service catalog (GET /v1/services is authoritative at run time).
**Spam reputation (`number.spam`, alias `spam`).** Whether a phone number appears in spam and nuisance-call
reports: telecom-regulator actions, government nuisance-call complaint data and community spam-report sites, plus
whether the number looks unassigned — recently offered as an unassigned number, or in a range the national
numbering plan has not assigned (a possible spoofed caller ID or fake lead) — and whether it is a premium-rate
number. It is report-based: `no_reports` means we hold no reports for the number — it is **not** a statement that
the number is safe. Countries: all, except sanctioned countries (see below). Attributes: `risk_level`
(`high | medium | low | no_reports`), `risk_score` (integer 0–100, higher = more reports or risk signals), booleans
`reason_regulator`, `reason_government`, `reason_community`, `reason_unassigned`, hint `voip_range` (VoIP carrier
range or VoIP number type; adds no points), `top_category` (most frequent report category; `telemarketing` = in a
range designated for telemarketing calls), `first_seen` / `last_seen` (YYYY-MM, when the number first/last appeared
in our data), `sources` (integer, independent signal classes), `premium_rate` (premium-rate or international
shared-cost number — a toll-fraud risk for OTP/verification traffic; adds 20 points but is not a signal class),
hint `personal_number` (personal/call-forwarding or pager number type; adds no points). Attributes may be added
over time; ignore unknown keys and enum values. Levels: `high` needs a regulator action or at least two
independent signal classes. Billing: every `risk_level` including
`no_reports` is a conclusive answer and is billed; `unknown` and `unsupported_country` are free. No report texts
and no names are ever returned.
**Live network status (`number.hlr`, alias `hlr`).** Live home-network query: `status`
(`reachable | unreachable | invalid | unknown`), `ported`, `roaming` (yes/no only, no location), `network`,
`mcc_mnc`, `country`. `reachable`, `unreachable` and `invalid` are conclusive and billed; `unknown` is free.
**Number portability (`number.mnp`, alias `mnp`).** Whether a mobile number was ported to another network:
`porting` (`ported | not_ported | unknown`), `mcc_mnc` and `country` of the current network. `ported` and
`not_ported` are billed; `unknown` (including invalid numbers) is free.
**Sanctioned countries.** Numbers from Cuba, Iran, North Korea, Syria, Russia, Belarus, Venezuela and sanctioned regions
are never checked:
every check answers `unsupported_country` and is free.'
humanURL: https://mobilevalidate.com/docs
baseURL: https://api.mobilevalidate.com/v1
tags:
- Catalog
tags_raw:
- catalog
properties:
- type: OpenAPI
url: openapi/mobilevalidate-com-catalog-api-openapi.yml
- type: JSONSchema
url: json-schema/mobilevalidate-com-service-schema.json
- aid: mobilevalidate-com:mobilevalidate-com-jobs-api
name: mobilevalidate-com Jobs API
description: Bulk checks for up to 50,000 numbers and e-mail addresses per job, with paginated results and downloads.
humanURL: https://mobilevalidate.com/docs
baseURL: https://api.mobilevalidate.com/v1
tags:
- Job
tags_raw:
- jobs
properties:
- type: OpenAPI
url: openapi/mobilevalidate-com-jobs-api-openapi.yml
- type: JSONSchema
url: json-schema/mobilevalidate-com-estimate-schema.json
- type: JSONSchema
url: json-schema/mobilevalidate-com-result-item-schema.json
- type: JSONSchema
url: json-schema/mobilevalidate-com-job-schema.json
- type: JSONSchema
url: json-schema/mobilevalidate-com-job-input-schema.json
- aid: mobilevalidate-com:mobilevalidate-com-keys-api
name: mobilevalidate-com Keys API
description: Instant personal test keys for developers (no account needed).
humanURL: https://mobilevalidate.com/docs
baseURL: https://api.mobilevalidate.com/v1
tags:
- Keys
tags_raw:
- keys
properties:
- type: OpenAPI
url: openapi/mobilevalidate-com-keys-api-openapi.yml
- aid: mobilevalidate-com:mobilevalidate-com-lookup-api
name: mobilevalidate-com Lookup API
description: Real-time checks for up to 100 numbers and e-mail addresses per request.
humanURL: https://mobilevalidate.com/docs
baseURL: https://api.mobilevalidate.com/v1
tags:
- Lookup
tags_raw:
- lookup
properties:
- type: OpenAPI
url: openapi/mobilevalidate-com-lookup-api-openapi.yml
- type: JSONSchema
url: json-schema/mobilevalidate-com-lookup-request-schema.json
- type: JSONSchema
url: json-schema/mobilevalidate-com-result-item-schema.json
- aid: mobilevalidate-com:mobilevalidate-com-system-api
name: mobilevalidate-com System API
description: Service health.
humanURL: https://mobilevalidate.com/docs
baseURL: https://api.mobilevalidate.com/v1
tags:
- System
tags_raw:
- system
properties:
- type: OpenAPI
url: openapi/mobilevalidate-com-system-api-openapi.yml
- aid: mobilevalidate-com:mobilevalidate-com-webhooks-api
name: mobilevalidate-com Webhooks API
description: Signed notifications (Standard Webhooks) when lookups and jobs finish. See the `webhooks` section for the event
payloads and https://mobilevalidate.com/docs/webhooks for signature verification.
humanURL: https://mobilevalidate.com/docs
baseURL: https://api.mobilevalidate.com/v1
tags:
- Webhook
tags_raw:
- webhooks
properties:
- type: OpenAPI
url: openapi/mobilevalidate-com-webhooks-api-openapi.yml
- type: JSONSchema
url: json-schema/mobilevalidate-com-webhook-endpoint-schema.json
- type: JSONSchema
url: json-schema/mobilevalidate-com-webhook-event-schema.json
x-enrichment:
date: '2026-10-31'
status: enriched
artifacts_added: 38
pass: modular-v1
engine: identity=local,contract=local,surfaces=local,docs=local,regulatory=local
mobilevalidate-com API — frequently asked questions
Does mobilevalidate-com have an API?
Yes. APIs.io lists 7 APIs from mobilevalidate-com, including mobilevalidate-com Account API, mobilevalidate-com Catalog API and mobilevalidate-com Jobs API, and 4 more.
Is there an OpenAPI specification for the mobilevalidate-com API?
Yes. APIs.io indexes 7 OpenAPI specifications for mobilevalidate-com, each linked for download from this page.
How do I authenticate with the mobilevalidate-com API?
mobilevalidate-com uses bearer-token authentication (1 scheme). The details are profiled on APIs.io as mobilevalidate-com Authentication.
Is the mobilevalidate-com API ready for AI agents?
mobilevalidate-com has a Kin Score of 61.5 out of 100 (strong) and an Agent Readiness score of 44.0 (agent-ready), scored by API Evangelist on 2026-11-13.
Calls without X-API-Key need no key. Calls with it need a paid plan — get a key.
Get an API key
Free tier, no form to fill in. Signing in shares your email address with us — we
store it to create your key and to recognise you if you sign in with another
provider. See our Privacy Policy and
Terms.