# Bird vs Twilio for Verify

Bird Verify keeps [channel routing and code checks](/docs/guides/verify/sending-verifications) on the recipient: send a code, advance the delivery plan and check the answer with the same email address or phone number.

[Get Started](/dashboard/signup?returnTo=%2Fdashboard%2Fw%2Fverify)

[Contact Sales](/demo?product=verify&source_page=%2Fverify-api%2Fcompare%2Fbird-vs-twilio)

## Set up with your agent

[Read the agent setup guide](/docs/ai/set-up-your-agent)

Copy this prompt into your coding agent:

```text
Bird connects customer communications, data and automation. Help me build with Bird using my coding agent.
1. Read https://bird.com/docs/ai/set-up-your-agent.md and follow its setup workflow for this client. Use an existing connected Bird MCP server or signed-in CLI when available.
2. Read the product guide for the task I want to complete and inspect my existing integration. Identify the workspace, available operations and required setup.
3. Help me complete a first example for the product and destination I choose. Follow the operation through to its actual result, explain any uncertainty, and help me choose the next step.

Use this Bird page as the starting context: https://bird.com/verify-api/compare/bird-vs-twilio
Read its Markdown alternative and linked guides. Keep the first example relevant to this page and the customer outcome I choose. Preserve the supplied campaign context when following Bird signup or sales links.
```

[Read customer stories](/customers)

[Explore Enterprise](/enterprise)

- [Airwallex](/customers/airwallex)
- [Glovo](/customers/glovo)
- [Zillow](/customers/zillow)
- Uber
- [Binance](/customers/binance)
- Adobe
- Meta
- PayPal
- Pinterest
- Square
- [Al Jazeera](/customers/aljazeera)
- [Aramex](/customers/aramex)
- [Bazaar Technologies](/customers/bazaar)
- [ComparaOnline](/customers/compara)
- [Emma](/customers/emma)

## Which verification flow fits your application?

### When Twilio Verify fits

- [Twilio’s verification resource](https://www.twilio.com/docs/verify/api/verification) accepts call and silent network authentication alongside SMS, WhatsApp and email. Keep a relied-on voice or SNA path with a provider that supports it; Bird’s [resolved channel plan](/docs/guides/verify/sending-verifications#options) supports SMS, WhatsApp, email and Telegram.
- [Twilio Services](https://www.twilio.com/docs/verify/api/service) group verification configuration, including code length and friendly name. The [create request](https://www.twilio.com/docs/verify/api/verification) also accepts a template, locale and custom code. Inventory those choices before moving to Bird’s workspace settings and built-in messages.
- Twilio’s [SMS riskCheck](https://www.twilio.com/docs/verify/api/verification) enables or bypasses active fraud protections per attempt, including Fraud Guard and Geo Permissions. Preserve the application’s risk decisions during migration rather than treating Bird’s resend and check limits as the same control.

### Why choose Bird Verify?

- Bird [resolves delivery from the recipient and country](/docs/guides/verify/sending-verifications#recipient). A request can trim or reorder the available plan with options.channels, and delivery failure can advance it automatically. The same recipient identifies the check and the next-channel request.
- Bird’s [check result](/docs/api/reference/create-verification-check) exposes success, reason and attempts_remaining. Use success: true to record the application’s verified state; an HTTP 200 can also carry an incorrect-code result.
- Bird’s [hosted MCP server](/docs/ai/mcp-server) and [CLI](/docs/cli) operate the same [Verify flow](/docs/guides/verify/sending-verifications): create, check and next-channel. An agent can request another delivery channel using the recipient already held by the application.

## How do the Verify APIs compare?

Compare the request and lifecycle controls your application uses. Channel availability depends on the recipient’s country and the account’s enabled capabilities.

| Capability | Bird | Twilio Verify | Who wins |
| --- | --- | --- | --- |
| Create request | [JSON with a bearer key](/docs/api/reference/create-verification) to /v1/verify/verifications; to contains an email address, phone number or both. | [Form-encoded create](https://www.twilio.com/docs/verify/api/verification) under a Service SID, with a recipient and channel. | Even |
| Safe retries | [Idempotency-Key](/docs/guides/idempotency) replays a request. [Recipient resends](/docs/guides/verify/sending-verifications#check-the-code) reuse the live verification, respect a cooldown and issue a fresh code after it. | [Twilio keeps the same token](https://www.twilio.com/docs/verify/api/rate-limits-and-timeouts) during its validity period until verification succeeds, including when another request arrives. | Even |
| What a failed check tells you | [success: false](/docs/api/reference/create-verification-check), a reason such as incorrect_code and attempts_remaining. Store success: true; a finalized verification returns 404 on another check. | [Verification Check](https://www.twilio.com/docs/verify/api/verification-check) returns status, including pending, approved and max_attempts_reached. Approved, expired and maximum-attempt verifications are deleted; a later check returns 404. | Bird |
| Channels a passcode can arrive on | [SMS, WhatsApp, email and Telegram](/docs/guides/verify/sending-verifications#options), restricted to the recipient’s resolved country plan. | [SMS, email, WhatsApp and call](https://www.twilio.com/docs/verify/api/verification); the same resource also offers sna and auto for silent authentication workflows. | Twilio Verify |
| Per-request configuration | [options.code_length, options.channels and options.language](/docs/guides/verify/sending-verifications#options); sender and default settings come from workspace configuration. | [Service selection plus request options](https://www.twilio.com/docs/verify/api/verification) for a template, locale, custom code and friendly name. | Twilio Verify |
| Hosted MCP server | [Authenticated hosted MCP](/docs/ai/mcp-server) runs [create, check and next-channel](/docs/guides/verify/sending-verifications); the bird CLI exposes the same operations. | [Twilio’s hosted docs MCP](https://www.twilio.com/docs/ai/mcp) searches and retrieves documentation without executing API calls. [Twilio Labs’ MCP proof of concept](https://github.com/twilio-labs/mcp/tree/main/packages/mcp) loads selected API services; the [Twilio CLI](https://www.twilio.com/docs/twilio-cli/quickstart) makes API requests. | Bird |
| Delivery events | [Session and attempt events](/docs/guides/verify/events) on workspace webhooks, signed with Standard Webhooks. Delivery and successful code use are separate events. | [Verify Events](https://www.twilio.com/docs/verify/verify-events) is Pilot with self-serve onboarding. It streams verification and message status for SMS, WhatsApp, RCS and Voice to a webhook or Amazon Kinesis. | Even |
| Channel fallback | [Delivery failure advances the resolved plan](/docs/guides/verify/events). The [next-channel operation](/docs/api/reference/create-verification-next-channel) lets the application advance it and sends a fresh code; earlier codes remain valid. | [Automatic SMS Fallback](https://www.twilio.com/docs/verify/automatic-channel-selection) tries SNA and falls back to SMS. Twilio labels it Pilot and requires contacting sales for access. | Even |

## Who advances fallback, and which code still works?

Bird advances the recipient’s resolved plan when a delivery fails. Your application can also call [next-channel](/docs/api/reference/create-verification-next-channel) when the user reports that no code arrived. Each call advances at most one channel and sends a fresh passcode; all earlier passcodes for that verification stay valid.

Bird: create with to → resolved plan → delivery failure or next-channel → fresh passcode → check with the same to. An exhausted plan returns NoNextChannel. Preserve a completed success before offering another send.

Twilio: create with Service SID and channel: auto → SNA attempt → SMS fallback when needed → Verification Check. [The automatic-channel guide](https://www.twilio.com/docs/verify/automatic-channel-selection) describes this specific SNA-to-SMS flow and labels access Pilot. [Twilio’s token](https://www.twilio.com/docs/verify/api/rate-limits-and-timeouts) stays the same throughout its validity period until success.

## What should your application store after a check?

Store the successful authentication outcome. Bird identifies a verification by the exact [to set](/docs/guides/verify/sending-verifications#check-the-code): if creation used both phone and email, repeat both. A response with success: false and reason: incorrect_code is a failed check even with HTTP 200. A later 404 E13000 cannot undo an earlier success: true.

[Twilio also accepts a recipient for checking](https://www.twilio.com/docs/verify/api/verification-check), or a Verification SID, under the Service SID. Use status: approved as its successful result. Its valid boolean is a legacy property; the reference directs integrations to status.

## Which abuse controls belong in the migration?

Bird’s [abuse guardrails](/docs/guides/verify/sending-verifications#abuse-guardrails) include a resend cooldown, recipient send cap and check-rate limits. Requesting the next channel bypasses the resend cooldown and hourly send cap, but the finite channel plan bounds advancement. Keep your own account and session risk controls around these operations.

[Twilio’s SMS riskCheck](https://www.twilio.com/docs/verify/api/verification) can enable or bypass Fraud Guard and Geo Permissions for an attempt. Map those settings and their operational decisions explicitly; a delivery retry limit does not establish equivalent fraud detection.

[SMS pricing](/sms-api/pricing)

[carrier fees](/pricing/sms/fees)

[Bird email pricing](/email-api/pricing)

[Bird WhatsApp pricing](/whatsapp-api/pricing)

## How are verification and delivery billed?

[There's no plan, seat, or platform fee for Bird Verify.](/verify-api/pricing) Each delivery is charged at that channel's rate for the destination. A resend, or a fallback that moves delivery to a second channel, is a new send and a new charge.

A verdict compares only published delivery rates with the same channel, destination, currency, billing unit and sender type. Per-success verification fees and per-send charges are Not comparable: your own sends and successful checks determine usage.

Pricing verdict: Not comparable

| Published item | Twilio Verify | Bird billing policy |
| --- | --- | --- |
| Base pricing. Per successful verification | [$0.05](https://www.twilio.com/en-us/verify/pricing) USD. Per successful verification plus standard channel fees. as published 2026-09-08 | [There's no plan, seat, or platform fee for Bird Verify.](/verify-api/pricing) Channel sends are billed separately. Check the live channel rates below. |
| SMS (US). Per SMS. Destination: US | [$0.0083](https://www.twilio.com/en-us/verify/pricing) USD. Per SMS (US). The successful-verification fee is charged separately. as published 2026-09-08 | [There's no plan, seat, or platform fee for Bird Verify.](/verify-api/pricing) Channel sends are billed separately. Check the live channel rates below. |
| WhatsApp (US). Per authentication template message. Destination: US | [$0.0034](https://www.twilio.com/en-us/verify/pricing) USD. Per authentication template message (US). The successful-verification fee is charged separately. as published 2026-09-08 | [There's no plan, seat, or platform fee for Bird Verify.](/verify-api/pricing) Channel sends are billed separately. Check the live channel rates below. |
| Voice. Per successful verification | [$0.05](https://www.twilio.com/en-us/verify/pricing) USD. Per successful verification. Voice channel pricing applies separately. as published 2026-09-08 | [There's no plan, seat, or platform fee for Bird Verify.](/verify-api/pricing) Channel sends are billed separately. Check the live channel rates below. [This method is outside Bird’s documented Verify channel plan.](/docs/guides/verify/sending-verifications#options) |
| Email. Per successful verification | [$0.05](https://www.twilio.com/en-us/verify/pricing) USD. Per successful verification. Email channel pricing applies separately. as published 2026-09-08 | [There's no plan, seat, or platform fee for Bird Verify.](/verify-api/pricing) Channel sends are billed separately. Check the live channel rates below. |
| Silent Network Auth. Per successful verification | [$0.05](https://www.twilio.com/en-us/verify/pricing) USD. Per successful verification plus per-country channel fee. as published 2026-09-08 | [There's no plan, seat, or platform fee for Bird Verify.](/verify-api/pricing) Channel sends are billed separately. Check the live channel rates below. [This method is outside Bird’s documented Verify channel plan.](/docs/guides/verify/sending-verifications#options) |
| Push. Per approved or denied request | [Push channel fee is included in the verification fee.](https://www.twilio.com/en-us/verify/pricing) . It’s charged when a request is approved or denied. as published 2026-09-08 | [There's no plan, seat, or platform fee for Bird Verify.](/verify-api/pricing) Channel sends are billed separately. Check the live channel rates below. [This method is outside Bird’s documented Verify channel plan.](/docs/guides/verify/sending-verifications#options) |
| TOTP. Per approved request | [TOTP channel fee is included in the verification fee.](https://www.twilio.com/en-us/verify/pricing) . It’s charged when a request is approved. as published 2026-09-08 | [There's no plan, seat, or platform fee for Bird Verify.](/verify-api/pricing) Channel sends are billed separately. Check the live channel rates below. [This method is outside Bird’s documented Verify channel plan.](/docs/guides/verify/sending-verifications#options) |
| Volume pricing. Custom volume | [Contact sales](https://www.twilio.com/en-us/verify/pricing) . Contact sales for volume-based discounts. as published 2026-09-08 | [There's no plan, seat, or platform fee for Bird Verify.](/verify-api/pricing) Channel sends are billed separately. Check the live channel rates below. |

## Bird published SMS channel rates

Bird's SMS catalogue rates are shown by sender type, per message segment. Carrier fees and sender costs may apply separately. These channel rates are not a total verification quote.

[SMS pricing](/sms-api/pricing); [carrier fees](/pricing/sms/fees).

| Destination | Sender type | Per SMS segment |
| --- | --- | --- |
| US | long_code | [EUR 0.003](/sms-api/pricing) |
| US | long_code | [USD 0.0035](/sms-api/pricing) |
| US | toll_free | [EUR 0.003](/sms-api/pricing) |
| US | toll_free | [USD 0.0035](/sms-api/pricing) |
| US | short_code | [EUR 0.006](/sms-api/pricing) |
| US | short_code | [USD 0.007](/sms-api/pricing) |

[Bird email pricing](/email-api/pricing) and [Bird WhatsApp pricing](/whatsapp-api/pricing) publish the other delivery channels.

## How do you start a verification?

[Twilio’s Node SDK](https://github.com/twilio/twilio-node/blob/main/src/rest/verify/v2/service/verification.ts) creates a verification beneath a Service. Bird’s [create endpoint](/docs/api/reference/create-verification) takes the recipient directly. Reuse the application’s idempotency key for retries of the same Bird request.

**Twilio Verify** · verify.ts

```typescript
import twilio from "twilio";

const client = twilio(process.env.TWILIO_ACCOUNT_SID!, process.env.TWILIO_AUTH_TOKEN!);

try {
  const verification = await client.verify.v2
    .services(process.env.TWILIO_VERIFY_SERVICE_SID!)
    .verifications.create({
      to:      "+15551234567",
      channel: "sms",
    });
  console.log(verification.sid, verification.status);
} catch (err) {
  console.error(err);
}
```

**Bird** · verify.ts

```typescript
import { BirdClient } from "@messagebird/sdk";

const bird = new BirdClient({ apiKey: process.env.BIRD_API_KEY! });

const { data, error } = await bird.verify.verifications
  .create(
    {
      to:      { phone_number: "+15551234567" },
      options: { code_length: 6, channels: ["sms"] },
    },
  )
  .safe();

if (error) console.error(error.message);
else console.log(data.id, data.status);
```

## Switching cost: What must change before cutover?

Inventory each Service’s channels, templates, risk rules and recovery path. Map supported recipients and configuration using the [Twilio migration guide](/docs/guides/verify/migrate/twilio). Retain or redesign any relied-on call, SNA or custom-message path that the Bird contract does not offer.

Cut over new creates, then route each check to the provider that issued its code until outstanding verifications expire. Persist the successful application outcome and test resend, next-channel, expired-code and exhausted-attempt behavior. Bird’s [sender guide](/docs/guides/verify/senders) shows the identities and messages users receive.

[Read the migration guide](/docs/guides/verify/migrate/twilio)

[See the Verify surface](/verify-api)

## What should you check before choosing?

### Is Bird a Twilio Verify alternative for SMS and email?

Bird [sends and checks codes](/docs/guides/verify/sending-verifications) for supported email and phone recipients, with country-based channel selection. Evaluate the actual destination plan and your recovery paths. Twilio’s [call and SNA options](https://www.twilio.com/docs/verify/api/verification) need a separate decision if your application relies on them.

### Does a second Twilio request generate a different code?

[Twilio says the token stays the same](https://www.twilio.com/docs/verify/api/rate-limits-and-timeouts) during its validity period until verification succeeds. Bird’s [recipient resend](/docs/guides/verify/sending-verifications#check-the-code) sends a fresh code after the cooldown, with earlier codes remaining valid for the live verification. Test code handling and retry behavior separately.

### Can I move every Twilio template and locale setting?

[Twilio’s create](https://www.twilio.com/docs/verify/api/verification) accepts template and locale options. Bird’s [options.language](/docs/guides/verify/sending-verifications#message-language) chooses a built-in translation, while the [message wording and senders](/docs/guides/verify/senders) follow Bird’s channel policy. Review the recipient-facing message before cutover.

### Does a 404 mean the user failed verification?

No. Bird’s [check endpoint](/docs/api/reference/create-verification-check) returns 404 E13000 when no active verification matches, including after completion. Twilio’s [Verification Check](https://www.twilio.com/docs/verify/api/verification-check) also returns 404 after an approved, expired or maximum-attempt verification is deleted. Keep the first successful result in your application.

## Where to go next

The migration guide is the one to start with: it maps the API field by field.

- [Migrate Verify from Twilio](/docs/guides/verify/migrate/twilio): Twilio Verify's Services, Verifications and VerificationCheck mapped onto Bird, with the settings that have no home called out.
- [Bird vs Prelude for Verify](/verify-api/compare/bird-vs-prelude): Compare recipient checks, routing policy and verification lifecycle.
- [Verify comparisons](/verify-api/compare): Compare the delivery and check workflows each provider publishes.
- [Verify pricing](/verify-api/pricing): Read how channel sends are billed and how resends affect usage.
- [Channel orchestration](/verify-api/features/orchestration): How the country plan decides which channel a passcode arrives on, and in what order.
- [Bird for AI agents](/docs/ai/mcp-server): The hosted MCP server, the bird CLI, agent skills, and the Markdown twins behind every docs page.

## Make verification part of your product.

Talk through your channels, verification flow, and expected traffic with our team.



## Related resources

- [Verify phone numbers at signup](/learn/series/verify-phone-numbers-at-signup) (video)
- [Verify your first customer](/docs/get-started/verify-your-first-customer) (docs)
- [What does OTP mean? One-time passwords explained](/explained/verify/what-does-otp-mean) (answer)
- [Build your first integration](/learn/paths/integration) (course)

[Get an implementation brief](/learn/workspace?topic=verify)