How to receive a Google verification SMS on asms.ai
The process takes under a minute. Go to asms.ai and browse the list of available phone numbers. Numbers are grouped by country, so if Google is asking for a number from a specific region, filter accordingly. Pick any number that shows recent activity, recent incoming messages are a reliable sign the number is still accepted by Google's systems.
Copy the number exactly as shown, including the country code, and paste it into the Gmail phone number field. Click 'Send code' in Gmail, then switch back to the asms.ai page for that number. The page refreshes automatically and your 6-digit Google verification SMS will appear, usually within 30 seconds. Type the code into Gmail and you're done.
There is no login step on asms.ai, no email confirmation, no waiting room. The number is public, the messages are public, and the code is right there on the page. The trade-off is that anyone else browsing the same number can see the same messages, which is why these shared numbers are ideal for low-sensitivity use cases like account setup, not ongoing personal correspondence.
Is it really free? What's the catch?
Yes, the shared numbers on asms.ai are genuinely free. There is no freemium bait, no 'free for 3 messages then pay', no requirement to create an account before a number starts working. The service is supported by a premium tier, private numbers and API access, but the free shared numbers are a fully functioning product, not a lead-gen demo.
The honest limitation is that the numbers are public. Because anyone can read messages sent to a shared number, you should not use one as a permanent number for a Google account holding sensitive data. Use it to get through the verification step, then optionally add your real number to the account for ongoing security. For creating throwaway accounts, testing applications, or any scenario where the number is a one-time tool, the shared free tier is exactly right.
There are no interstitial ads to click through before you can see a message, no SMS previews hidden behind a paywall, and no countdown timers. The messages appear on the page and you read them. If you need a number exclusively yours, one that won't have other people's messages mixed in, asms.ai's private number plans cover that at a modest monthly fee.
Why people specifically need a phone number for Gmail
Google uses SMS verification when creating a new account, adding recovery options, signing in from an unrecognised device, and unlocking a flagged account. In every case, Google sends a one-time code to a number you supply. The code expires quickly, so the message needs to arrive fast and be immediately readable.
Many users want a phone number for Gmail that isn't linked to their real identity. Privacy is the most common reason, mobile numbers are persistent identifiers that can be cross-referenced across services. Others are outside their home country without a local SIM, or they're developers who need to spin up multiple test accounts without burning through personal phone numbers. Some simply don't want a second Gmail address tied to the same number as their primary account.
Whatever the reason, the requirement is the same: a real working number that Google will accept, that can receive an SMS, and that you can read right now. asms.ai's shared numbers meet all three criteria.
Privacy and security, what you should know
When you receive SMS for Gmail using a shared public number, the transaction is private in one direction and transparent in another. Google sees the phone number, not your name or IP address. asms.ai does not ask for any identifying information, and there is no account linking you to the number you used, from Google's perspective, someone entered a number and received a code.
The transparency side is that messages on shared numbers are public. Anyone visiting that number's page can read every SMS that arrives. For a Gmail verification code, this rarely matters in practice: the code is 6 digits, expires in minutes, and has no value after it's been entered. If you're concerned about someone reading the code before you do, act quickly, paste the number into Gmail, switch immediately to asms.ai, and use the code as soon as it appears.
For anything requiring a higher level of security, a primary Google account, Google Workspace, or an account holding sensitive data, use your personal number or opt for a private number. The shared free tier is built for convenience in low-stakes scenarios, and it does that job well.
Which countries' numbers work with Gmail?
asms.ai maintains numbers from the United States, the United Kingdom, Germany, Georgia, and Ukraine, with new numbers added regularly. Google generally accepts numbers from any country where it operates, so a US number works for a US Gmail setup, a UK number works for a British Google account, and so on.
Country availability matters because Google sometimes restricts which regions' numbers it will accept depending on the account's locale or the type of verification being performed. If one country's numbers aren't being accepted, try a different country, the site makes it easy to switch. Numbers showing recent activity, visible from the timestamp on each number's page, tend to have the highest acceptance rate.
New numbers are added daily to counteract the natural churn of numbers that Google eventually flags as over-used. If a number is being rejected, move to a freshly listed one. The inventory is kept live precisely for this reason.
What else can you use these numbers for?
While this page focuses on Gmail and Google account verification, the same numbers work across hundreds of services that require SMS-based verification. Common uses include creating accounts on social platforms, verifying marketplace registrations, signing up for software trials, and onboarding to any service that demands a phone number you'd rather not give permanently.
Google services beyond Gmail, including Google Voice, Google Pay, and Google Play, also send verification codes by SMS and work the same way. Developers integrating Google APIs who need to test OAuth flows with multiple accounts find asms.ai useful since they can cycle through available numbers without managing a stack of physical SIM cards.
One caveat: these numbers are not suited for services that send ongoing authentication messages, long-term two-factor codes, or anything where you need to reliably receive future messages to the same number. Shared numbers are periodically cleared of old messages and the pool rotates over time. For persistent use, the private number tier is the right choice.
Developers and AI agents: the API and MCP server
If you're building an application, running automated tests, or working with AI agents that need to receive SMS codes, asms.ai offers a REST API that gives programmatic access to numbers and incoming messages. Instead of polling a web page, your code calls the API and gets the SMS data back directly, structured, fast, and scriptable.
There is also a native MCP (Model Context Protocol) server, meaning AI agents in compatible environments can use asms.ai as a tool natively. An agent that needs to create and verify a Google account as part of a workflow can call the MCP endpoint, pick a number, pass it to Google, and read the code back, all without human involvement. This is particularly useful in CI/CD pipelines and autonomous agent workflows.
API access and private numbers are the paid tier. Pricing is transparent and listed on the site. For casual human use, the free shared numbers remain completely free and require no API key, visit /api-docs for the full reference.