# Verify a user's phone number with a one-time code

> Verify a user's phone number with a one-time code: 1 companies fully do it, 10 with a limit, 41 carry the tag. Every listing in Messaging APIs with the reason and a source.

- Canonical: https://www.anchorterminal.com/niches/messaging.verify-phone-code/
- Markdown: https://www.anchorterminal.com/niches/messaging.verify-phone-code/index.md (~1,600 tokens)
- Slim: https://www.anchorterminal.com/niches/messaging.verify-phone-code/index.min.md (~280 tokens, same facts, less prose, for token-sensitive contexts)
- JSON: https://www.anchorterminal.com/niches/messaging.verify-phone-code/index.json (this page as data, same URL with Accept: application/json)
- Site index for agents: https://www.anchorterminal.com/llms.txt (the key docs and every listing in one file, at most 16 MB, about 4 million tokens: https://www.anchorterminal.com/llms-full.txt)
- API: https://www.anchorterminal.com/api/v1/index.json
- MCP: https://www.anchorterminal.com/mcp (the whole catalogue as tools, no key)
- DNS: dig +short TXT <slug>.grade.anchorterminal.com (the grade as a DNS TXT record, for a sandbox with no HTTP where names still resolve; also top., best.<category>. and <a>.vs.<b>. under the zone, and the same under grade.letme.dev)
- Licence: CC BY 4.0, credit Anchor Terminal and link this page (https://www.anchorterminal.com/terms/#data)
- Updated: 2026-11-15

One company's docs show a full fit.

| Companies, full fit | With a limit | Carry the tag | Share of the category's work | First-hand accounts |
| --- | --- | --- | --- | --- |
| 1 | 10 | 41 | 5 | 3 |

## What counts as done

A code delivered by SMS or WhatsApp, a check call that returns approved or denied, and requests to high-risk or premium destinations blocked before any charge.

Measured, for our own tests: the code is delivered within 30 seconds.

How agents ask for it: send a verification code to this number; add phone sign-up; check the code the user typed

## Does the job

The docs show it meets the test above, and nothing we read says otherwise.

- **Prelude (DING SAS)**: Create a verification returns blocked when anti-fraud rules fire, before a message goes, and a check call confirms the code; test numbers simulate it free. No delivery-time figure was found against the 30-second bar.

## Does the job, with a limit

It does the job, but something in the docs or a user's account will get in an agent's way. The limit is named in each row.

- **AWS End User Messaging (Amazon Web Services, Inc.)**: Notify sends passcodes with a managed protect configuration, and Protect blocks countries or filters pumping traffic at extra cost. An AWS-side check call was announced but not in the API model on 1 November.
- **Bandwidth Messaging API + MCP (Bandwidth Inc.)**: The MFA API sends a code by SMS or voice and has a verification call. No pumping or premium-destination blocking was found for it.
- **Bird API + MCP (Bird B.V.)**: Verify sends a code and checks it in two calls, keyed by recipient, with no sender to register. SMS fraud-protection blocks show in delivery errors, but no Verify-specific pumping or premium-destination rule was found.
- **Infobip API + MCP (Infobip Ltd)**: The 2FA API sends and verifies PINs over SMS, voice or email, with attempts and time to live set per application; Number Risk Score and Signals exist, but a pre-charge block on pumped destinations wasn't documented in what rendered.
- **Plivo API (Plivo Inc.)**: The Verify Session API sends an OTP by SMS or voice and validates it, and Fraud Shield blocks suspected pumping with error 452. No delivery-time figure, and the docs don't say whether blocked attempts are charged.
- **Sinch Messaging APIs + MCP (Sinch AB (publ))**: The Verification API sends and checks SMS and other verification methods with SDKs; no SMS-pumping or premium-destination block was found in the index.
- **Telnyx API + MCP (Telnyx LLC)**: The Verify API sends OTPs by SMS, voice or WhatsApp and checks them, with whitelisted destination countries; the fraud guide puts rate limits and anomaly checks on the caller's server rather than blocking pumping itself.
- **Twilio API + MCP (Twilio Inc.)**: Verify sends and checks codes, and Fraud Guard blocks suspected pumping at Basic, Standard or Max. acc-15 failed the 2FA campaign registration twice, and acc-16 had a pumping attack recharge the card every second on plain SMS.
- **Vonage Messages API + MCP (Vonage Holdings Corp.)**: Verify v2 runs workflows across silent auth, SMS, voice, WhatsApp and email and checks the code, and the product page names an anti-fraud system; whether it blocks before charging wasn't documented in the pages read.
- **YCloud (YCloud International Pte. Ltd.)**: POST /verify/verifications sends a code and /verify/verificationChecks checks it; no fraud or pumping protection appears anywhere in the spec.

- not this job: 360dialog WhatsApp API + MCP (360dialog GmbH): Authentication templates deliver a code over WhatsApp, but there is no check call and no fraud or pumping protection; the app verifies the code itself.
- not this job: ClickSend SMS API + MCP (ClickSend Pty Ltd): The Verification API covers account password and username recovery only; there is no one-time-code send and check, so the agent builds it on plain SMS.
- not this job: Kudosity (Known Pty Ltd): No verification product; the only verification calls confirm ownership of a sender number.
- not this job: Linq (Linq App Inc.): No verification product; Linq is a conversational line, not an OTP service.
- not this job: Photon (Something Great Inc.): No verification product; the beta SMS best-practices page notes the absence of general OTP filtering.
- not this job: Sendblue (Round One, Inc.): No verification product in the docs index; the capabilities tag's verify isn't backed by an endpoint.
- not this job: Telegram Bot API (Telegram Messenger Inc.): The Bot API has no code send and check; Telegram's separate Gateway product is not this listing.
- not this job: Wati (Clare.AI Limited): No verification product; authentication templates would be the app's own code check, with no fraud blocking.
- not this job: WhatsApp Business Platform (Cloud API) (Meta Platforms, Inc.): Authentication templates deliver a code, but there is no check call or pumping protection; the app stores and checks the code, and acc-41 saw an authentication message marked sent but never delivered.

## What stops agents finishing

- SMS pumping drains credit with auto-recharge and no cap
- 2FA campaign registration fails
- code message accepted but not delivered

## Around it

Before: agent-auth.signup-flow. After: identity-verification.check-identity.

## Where this comes from

Weight 5 of 100 in Messaging APIs: 3 of 69 accounts; raised above the count because 14 of 20 listings carry messaging.verify and Prelude and Twilio Verify are sold for it

As data: https://www.anchorterminal.com/api/v1/use-cases/messaging.verify-phone-code.json, or the MCP tool get_use_case with id messaging.verify-phone-code. Draft, read 2026-11-15 from public docs and first-hand accounts, not yet reviewed by a person.

---

Query this catalogue directly over MCP: https://www.anchorterminal.com/mcp (Streamable HTTP, no key). How: https://www.anchorterminal.com/agents/#mcp
