AI automation

Phone verification API for AI agents

Numberly Relay · One API for agents to rent phone numbers and read SMS codes in any country

WatchingDraft scoreMature market · since 2010 · AI estimate

27PWAS score

Confidence

Based on 8 of 9 factors

Overview

AIThis description was written by a model from public signals. The facts behind it are listed under Evidence.

Problem: AI agents need phone numbers to complete SMS verification flows when automating tasks that require account creation or identity confirmation, but obtaining numbers programmatically across multiple countries is complex and fragmented.
Solution concept: A unified phone verification service that allows AI agents to order virtual phone numbers from 200+ countries through a single API, automatically receive SMS codes, and return them to the agent—eliminating the need to integrate multiple providers or accept geographic limitations.
Who has it: AI agent developers and teams building autonomous systems that need to automate account creation, identity verification, or other flows requiring SMS verification codes across different countries.
How they handle it today: AI agents currently either lack a way to programmatically obtain phone numbers for verification, cobble together solutions from multiple providers, or are limited to a small set of countries where verification services are available.
Why now: AI agents are becoming more capable and autonomous, with frameworks like Claude, Cline, and others enabling broader automation use cases that require completing real-world verification flows; demand from developers building these systems is growing.
How it could charge: Charge per SMS received, per number ordered, or through a subscription tier based on usage volume or geographic reach; pricing would likely reflect the cost of acquiring numbers in different countries.

Verdict

Computed from the factor scores below, never written by a model. It decides nothing on its own: only the gate makes an opportunity a build candidate.

Score breakdown

A model sorted each factor into a rubric bucket; code turned buckets into numbers. Unknown factors are left out of the score and lower confidence instead.

Market validation

Confidence 70 · 1 evidence · The evidence confirms AI agents need phone verification across countries, but no established competitors or multiple active products are named.

Revenue evidence

Unknown

No evidence of paid customers, revenue claims, or monetization traction; only a pricing model concept is described.

Growth

Confidence 95 · 1 evidence · 545 stars in 67 days shows visible momentum for the GitHub project, indicating fast-growing interest.

Problem severity

Confidence 30 · Judged from the description · Automating account creation and identity verification across countries is costly friction that blocks autonomous workflows when manual intervention is required.

Economic proximity

Confidence 30 · Judged from the description · The product sits directly on account creation and automation workflows—a direct input to revenue-generating autonomous systems.

Distribution

Confidence 30 · Judged from the description · A backend API used privately by agent developers; the product itself is not exposed to end users or creates viral loops.

Buildability

Confidence 30 · Judged from the description · Requires integration with telecom providers across 200+ countries and SMS receiving infrastructure, which is complex but not research-grade.

Differentiation

Confidence 70 · 1 evidence · Wider geographic coverage than competitors is a clear gap users name; incumbents leave geographic limitations open.

Retention and timing

Confidence 30 · Judged from the description · Usage is recurring within any agent's continuous automation workflows; AI agent adoption is a clear timing tailwind.

Risk penalties

Questionable data accessObtaining virtual phone numbers across 200+ countries for account creation and bypassing verification flows may violate terms of service, anti-fraud rules, or data protection laws in jurisdictions where the service operates.−15
Heavy regulationTelecom services and SMS aggregation are regulated in many countries; identity verification spans financial and compliance domains with varying legal requirements.−9
Extreme competitionThe evidence acknowledges competing solutions with geographic coverage; established telecom aggregators and SMS providers already serve this use case across multiple countries.−6

Score history

27 · confidence 41 · config v1First score · 14 Oct 2026

Phone verification API for AI agents

Overview

Verdict

Build this business

Score breakdown

Risk penalties

Score history

Validation gate

Evidence · 3 items

Market validation

Growth

Differentiation

Market

Existing products

Build

Legal reconstruction check

Community