Opportunities › Phone verification API for AI agents › Proposed app
Numberly Relay
One API for agents to rent phone numbers and read SMS codes in any country
- Score
- 27
- confidence 41
- Evidence
- 3
- items on the page
- Rivals
- 1
- named in sources
- First version
- 30 d
- estimate
- Type
- Desktop app
- PWA: runs in the browser, installs on Mac and Windows
- Market since
- 2010
- Mature market · AI estimate
ScreensConcept
Desktop app: Developers integrate APIs and configure agents at a desk with dense configuration, logs, and monitoring dashboards. Sample screens on a computer, in the proposed brand. Their numbers are sample data.
New order
Waiting for SMS+54 …
- Country
About this appAI proposal
Numberly Relay gives AI agents a phone number when a flow asks for an SMS code. The agent makes one API call with a country and a service, gets a number, waits, and receives the code as plain JSON. No separate accounts with several number providers.
It is built for developers and teams who run autonomous agents that must confirm identity or finish sign-ups in more than a handful of countries. Each order has a time limit, a clear status and a refund if no code arrives.
What sets it apart: one request shape for every country, agent-friendly tool definitions you can drop into an agent framework, and a spend cap per agent so a loop gone wrong cannot drain your balance. You should only use it for accounts and flows you are allowed to automate.
- Tagline
- A phone number for your agent, wherever the flow asks for one.
- Voice
- PlainPreciseDependable
- Why this name
- A number is handed over and the code is relayed back to the agent. Two plain words that say what happens.
In the first version
Members say which features they would use. It tells PWAS what people want; it changes no score.
One call, any country
Order a number by country code and service. The same request works everywhere, so the agent needs no per-country logic.
No member yet
Code delivery as JSON
Poll or receive a webhook when the SMS arrives. The code is extracted and returned with the full message text.
No member yet
Agent tool definitions
Ready-made tool schemas and an MCP-style server so agents can order and read numbers without custom glue code.
No member yet
Auto refund on no code
If no message arrives before the order expires, the charge is released automatically and the number is retired.
No member yet
Brand identityAI proposal
Check the name against trademark registers before using it.
Palette
#0F4C5CDeep Teal · primary#F6F3ECPaper · surface#16232AInk · text#E8742CSignal Orange · accent#9DB8BFMist · data
Typography
Aa
Numberly Relay
ABCDEFGHIJKLMNOPQRSTUVWXYZ 0123456789
A phone number for your agent, wherever the flow asks for one.
PricingAI proposal
The material gives no competitor prices. These tiers are a starting point to test; per-order rates would follow the cost of numbers in each country.
Free
Free
- Test mode with sandbox numbers
- 1 API key
- Community support
Pay as you go
Free
- Per-order pricing by country
- Unlimited API keys
- Spend caps and webhooks
- Auto refund on no code
Team
$49 a month
- Discounted per-order rates
- Usage export and audit log
- Priority support
- Shared team balance
Would you pay Team · $49 a month?
Your answer tells PWAS which prices people accept. It changes no score.
No answers yet.
What it could be worthEstimate
What a software business making this much sells for today, from real deals. Pick a monthly revenue.
If it makes
Worth about
$194,000
Sale range $132,000 to $263,000
$120,000 a year in revenue
From 87 software businesses listed and sold on Empire Flippers in the last year, revenue vetted by the broker: they sell for about 19× their monthly revenue, most between 13× and 26×.
Measured on profit, the middle deal is 32× monthly net profit: about 2.7 years of profit.
An estimate, not an offer or financial advice. A real price depends on profit, growth, churn, how much of the work is the owner's, and the buyer.
How it would growAI proposal
How the product would reach new customers through its own use, and how the first ones would be found. A plan to test, not a result.
- Built-in loop
- Partners and integrations. Publish tool definitions and an MCP-style server for popular agent frameworks, plus open examples on GitHub. Developers find it from inside the tools where they build agents.
- Do they become customers?
- Developers who install an integration can become paying customers directly by topping up a balance. Test whether open-source examples convert to paid top-ups.
- First customers
- Solo developers and small teams building browser or task agents that need sign-up and identity flows in several countries.
- Where to reach them
- GitHub: Open-source client libraries and agent examples with clear docs, aimed at people already starring agent repositories.
- Agent framework communities: Share tool definitions in Discord and forum threads where builders ask about SMS verification.
- First milestone
- Twenty developers each top up a balance and run 50 or more paid orders in the first month.
Why people already pay for this
- VerifiedGitHub repository gained 545 stars in 67 days
- Public claimAI agents need a phone number to complete SMS verification across multiple countries
- Public claimThe product offers wider geographic coverage than competing solutions
Tech stack
Every proposal builds on the same PWA base, installable from the browser on any phone or computer. Dashed boxes are what this app adds.
- AppNext.js and TypeScript
- PWAManifest and service worker
- UITailwind CSS
- Data and authSupabase Postgres
- PaymentsStripe
- EmailResend
- HostingVercel
- This app · Number and SMS supplyWholesale virtual number and SMS provider APIsNumbers across 200+ countries must come from upstream carriers or aggregators; the product routes and resells them.
- This app · Job queue and timersDurable background job runnerOrder expiry, polling for inbound SMS and refunds need reliable scheduled work beyond request handlers.
RisksAI inference
- RegulatoryVirtual numbers used to bypass verification may breach platform terms or local telecom and anti-fraud rules. Abuse screening and acceptable-use enforcement are needed.
- PlatformMany services block virtual numbers, so success rates vary by country and sender and may drop without notice.
- CommercialMargins depend on upstream wholesale prices and on reselling a supply that others can also reach. Wider coverage may be copied.
- DataReceived messages can hold personal data or codes for other people's accounts. Retention limits and access controls are required.
- TechnicalUpstream providers fail or run out of stock. Routing across suppliers and honest refunds are needed to keep trust.
Everything marked AI proposal or AI inference was written by a model from the evidence on the opportunity page. The proposed name must be checked against trademark registers before it is used.