{
  "data": null,
  "kind": "anchor.page",
  "links": {
    "api": "https://www.anchorterminal.com/api/v1/index.json",
    "html": "https://www.anchorterminal.com/niches/messaging.verify-phone-code/",
    "json": "https://www.anchorterminal.com/niches/messaging.verify-phone-code/index.json",
    "llms": "https://www.anchorterminal.com/llms.txt",
    "markdown": "https://www.anchorterminal.com/niches/messaging.verify-phone-code/index.md",
    "mcp": "https://www.anchorterminal.com/mcp",
    "slim": "https://www.anchorterminal.com/niches/messaging.verify-phone-code/index.min.md"
  },
  "markdown": "One company's docs show a full fit.\n\n| Companies, full fit | With a limit | Carry the tag | Share of the category's work | First-hand accounts |\n| --- | --- | --- | --- | --- |\n| 1 | 10 | 41 | 5 | 3 |\n\n## What counts as done\n\nA 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.\n\nMeasured, for our own tests: the code is delivered within 30 seconds.\n\nHow agents ask for it: send a verification code to this number; add phone sign-up; check the code the user typed\n\n## Does the job\n\nThe docs show it meets the test above, and nothing we read says otherwise.\n\n- **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.\n\n## Does the job, with a limit\n\nIt 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.\n\n- **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.\n- **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.\n- **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.\n- **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.\n- **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.\n- **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.\n- **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.\n- **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.\n- **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.\n- **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.\n\n- 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.\n- 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.\n- not this job: Kudosity (Known Pty Ltd): No verification product; the only verification calls confirm ownership of a sender number.\n- not this job: Linq (Linq App Inc.): No verification product; Linq is a conversational line, not an OTP service.\n- not this job: Photon (Something Great Inc.): No verification product; the beta SMS best-practices page notes the absence of general OTP filtering.\n- 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.\n- 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.\n- not this job: Wati (Clare.AI Limited): No verification product; authentication templates would be the app's own code check, with no fraud blocking.\n- 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.\n\n## What stops agents finishing\n\n- SMS pumping drains credit with auto-recharge and no cap\n- 2FA campaign registration fails\n- code message accepted but not delivered\n\n## Around it\n\nBefore: agent-auth.signup-flow. After: identity-verification.check-identity.\n\n## Where this comes from\n\nWeight 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\n\nAs 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.\n",
  "meta": {
    "attribution": "Anchor Terminal (https://www.anchorterminal.com)",
    "attributionRequired": true,
    "credit": "CC BY 4.0, credit Anchor Terminal and link the page or API address you took it from (https://www.anchorterminal.com/terms/#data)",
    "docs": "https://www.anchorterminal.com/docs/",
    "generatedAt": "2026-11-16",
    "license": "CC-BY-4.0",
    "method": "https://www.anchorterminal.com/benchmark/",
    "methodology": "0.8",
    "openapi": "https://www.anchorterminal.com/openapi.json",
    "preview": false,
    "run": "2026-10-01",
    "runLabel": "October 2026 research run",
    "terms": "https://www.anchorterminal.com/terms/#data"
  },
  "page": {
    "breadcrumbs": [
      {
        "name": "Home",
        "url": "https://www.anchorterminal.com/"
      },
      {
        "name": "For agents",
        "url": "https://www.anchorterminal.com/agents/"
      },
      {
        "name": "Niches",
        "url": "https://www.anchorterminal.com/niches/"
      },
      {
        "name": "Verify a user's phone number with a one-time code",
        "url": ""
      }
    ],
    "description": "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.",
    "facts": null,
    "h1": "Verify a user's phone number with a one-time code",
    "image": "https://www.anchorterminal.com/assets/og/default.png",
    "path": "/niches/messaging.verify-phone-code/",
    "published": "",
    "section": "agents",
    "title": "Verify a user's phone number with a one-time code | Anchor Terminal",
    "toc": null,
    "updated": "2026-11-15",
    "url": "https://www.anchorterminal.com/niches/messaging.verify-phone-code/"
  },
  "tokens": {
    "markdown": 1600,
    "slim": 280
  },
  "version": 1
}
