> ## Knowledge Base Index
> Fetch the complete knowledge base index at: https://help.tuco.ai/sitemap.xml
> Use this file to discover available pages before exploring further.
> Pure-Markdown content can be obtained by appending a '.md' suffix to the content URLs listed in the sitemap (without the trailing slash).

# Can I use Tuco AI for automating OTP (one-time-passwords)?

Yes. You can send OTPs programmatically through the Tuco API from your dedicated number, the same way you send any other message.

## How it works

Your application calls `POST /api/messages` with the recipient and the code. The OTP arrives as an iMessage from your Tuco number, with SMS fallback available for contacts not on iMessage (listen for the `message.fallback` webhook to route those through your SMS provider).

| More API information is available at docs.tuco.ai 

Because the message comes from a real dedicated number rather than a shortcode pool, your verification messages arrive from the same number your customers already know and message with.

## The pricing question

Whether Tuco is the right fit depends on your volume:

**Transactional or moderate volume** (login codes for your app, verification during onboarding, appointment confirmations): Tuco works well. Your dedicated line handles OTPs alongside your regular conversations at plan pricing.

**Bulk OTP volume** (thousands of codes per day as your primary use case): Tuco's per-line pricing is built for conversational messaging, not high-volume transactional delivery, so the economics will not work in your favor. For dedicated bulk OTP delivery, take a look at [otpblue.com](https://otpblue.com). We are not affiliated with them, but they are purpose-built for that workload.

## Not sure which bucket you are in?
Message us with your expected daily OTP volume and we will give you a straight answer on whether Tuco pricing makes sense for your case.