Bird vs Prelude
Prelude Verify comparison
Switch verification channels in Bird while keeping the same recipient and code-checking flow.
recipient-addressed passcode delivery and verification · Prelude's verification window and fraud risk verdicts
Drag an icon onto the dots. Use arrow keys to move a focused icon. Press Escape to cancel a drag.
Trusted by engineering and product teams shipping at global scale.
Which verification flow fits your application?
When Prelude fits
Prelude's verification creation response returns a risk status such as allowed, retry, challenged, blocked, or shadow-blocked based on device and network signals. If your signup flow branches on that fraud verdict before sending a passcode, keep that risk check in your stack when moving code delivery.
Prelude supports RCS, Viber, Zalo, and silent network authentication alongside SMS, WhatsApp, Telegram, and voice calls. Bird's channel routing plan currently delivers over SMS, WhatsApp, email, and Telegram while voice OTP rolls out, so teams relying on RCS, Viber, Zalo, or silent network checks should plan for those channels before switching.
Prelude's verification request accepts per-request template IDs, locales, sender IDs, custom passcodes, and automatic fallback caps when enabled on the account. Review which of those per-request overrides your app uses before mapping them to Bird's workspace-level sender and routing rules.
Why choose Bird Verify?
Bird addresses each verification by the recipient, accepting an email address, a phone number, or both in a single request. Your workspace country plan selects the available channels, and each request can narrow or reorder that list.
Bird's verification check response tells your application whether the code matched, why a check failed, and how many attempts remain so your UI can show a helpful error message.
Bird's hosted MCP server and CLI let engineers and AI agents start verifications, check codes, and trigger next-channel fallbacks using the same recipient phone number or email address.
How do the Verify APIs compare?
Compare how each API handles recipient addressing, retry safety, channel fallback, and risk checks.
| Capability | Bird | Prelude | Who wins? |
|---|---|---|---|
| Create request | BirdSend a JSON request with a bearer key passing the recipient's email address, phone number, or both. | PreludeSend a JSON create-or-retry request with a bearer key, target type, and recipient value. Email verification requires account enablement. | Even |
| Safe retries | BirdAn idempotency header prevents duplicate sends on network retries, while recipient resends reuse the active session and send a fresh code after the cooldown. | PreludeRepeating the create call within an active verification window triggers a retry attempt subject to cooldown spacing and attempt caps. | Even |
| What a failed check tells you | BirdReturns the verification outcome, failure reason, and remaining attempt count so your UI can distinguish a typo from a locked session. | PreludeReturns a check status of success, failure, or expired-or-not-found, plus transaction-binding mismatch statuses for PSD2 flows. | Bird wins |
| Channels a passcode can arrive on | BirdSMS, WhatsApp, email, and Telegram governed by your per-country routing plan, with voice OTP rolling out. | PreludeSMS, RCS, WhatsApp, Telegram, Viber, Zalo, and silent network checks, plus voice call delivery. | Prelude wins |
| Delivery events | BirdWorkspace webhook subscriptions emit separate session and delivery attempt events signed with Standard Webhooks. | PreludePer-request callback URLs receive webhook events signed with RSASSA-PSS SHA-256 once a signing key is created. | Even |
| Fallback control | BirdFailed deliveries advance the country plan automatically, and the next-channel endpoint lets users request a backup channel while keeping earlier codes valid. | PreludeAn automatic fallback cap limits automatic channel retries when enabled on the account, with manual retries resetting that allowance. | Even |
| Hosted MCP server | BirdAn authenticated hosted MCP server and the Bird CLI run verification creation, code checks, and channel fallback. | PreludeServer SDKs including the Node SDK expose verification creation and code checks for backend code. | Bird wins |
| Code length | BirdSet the passcode digit length per request or fall back to your workspace default. | PreludeSet a 4-to-8-digit passcode size per request or use the dashboard default. | Even |
| Risk outcome | BirdEnforces per-recipient send caps, check attempt limits, and country allowlists without returning a device-level fraud verdict on creation. | PreludeReturns a fraud status and risk factors when device or network signals trigger a challenged, blocked, or shadow-blocked decision. | Prelude wins |
Who controls the next delivery attempt?
Bird builds the delivery sequence from the recipient and destination country. When a message fails to deliver, or when the user clicks to try another channel, Bird steps forward to the next configured channel through automatic or user-requested channel advancement, sending a fresh passcode while keeping earlier codes valid until the session expires.
In Prelude, your app submits the target and device signals, receives a fraud verdict, and enters an active verification window where Prelude's lifecycle guide treats another create call for the same phone number as a retry. Prelude's automatic fallback cap bounds how many extra automatic attempts run after the initial send, and setting it to zero turns off automatic retries so your application controls resends explicitly.
What does success mean in each response?
Bird's verification check endpoint returns an explicit boolean indicating whether the passcode was accepted, alongside a failure reason and remaining attempt count when a user enters the wrong digits. Persist the verified state in your database as soon as the check succeeds, because checking a completed session again returns a not-found error.
In Prelude, a successful verification creation response confirms that the verification window opened and the message was dispatched, so your application must wait for a successful code check response before signing the user in. Prelude's check endpoint also supports transaction-bound passcodes for PSD2 payment confirmation when your flow binds OTPs to payment amounts or payees.
Which risk signals and webhook checks must survive migration?
Prelude's create endpoint accepts a dispatch identifier from its frontend SDK, and its fraud protection guide combines server-side IP and user-agent headers with device signals to return challenged or shadow-blocked outcomes. Audit where your signup or login controller branches on those statuses before switching providers.
Bird's built-in abuse guardrails enforce resend cooldowns, per-recipient send limits, and maximum check attempts, while leaving device-fingerprinting or signup risk scoring to your application.
Prelude signs webhook deliveries using RSASSA-PSS SHA-256 headers, whereas Bird signs workspace webhooks with Standard Webhooks. Swap the signature verification middleware when you cut over your webhook handler.
How are verification and delivery billed?
There's no plan, seat, or platform fee for Bird Verify. 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 | Prelude | Bird billing policy |
|---|---|---|
| Pay As You Go Per verification | 0.032 € Per verification plus message costs. Monthly billing and 10,000 verifications selected. as published | There's no plan, seat, or platform fee for Bird Verify. Channel sends are billed separately. Check the live channel rates below. |
| Startup Per month | 360 € Per month plus message costs. Monthly billing and 10,000 verifications selected. as published | There's no plan, seat, or platform fee for Bird Verify. Channel sends are billed separately. Check the live channel rates below. |
| Enterprise Custom volume | Contact sales Contact sales for committed volume pricing. as published | There's no plan, seat, or platform fee for Bird Verify. Channel sends are billed separately. Check the live channel rates below. |
| SMS (US) Per SMS Destination: US | €0.0043 EUR Message cost for the selected United States destination. Verification charges are separate. as published | There's no plan, seat, or platform fee for Bird Verify. Channel sends are billed separately. Check the live channel rates below. |
| WhatsApp (US) Per message Destination: US | €0.0028 EUR Message cost for the selected United States destination. Verification charges are separate. as published | There's no plan, seat, or platform fee for Bird Verify. Channel sends are billed separately. Check the live channel rates below. |
| RCS (US) Per message Destination: US | €0.00 EUR Message cost for the selected United States destination. Verification charges are separate. as published | There's no plan, seat, or platform fee for Bird Verify. Channel sends are billed separately. Check the live channel rates below. This method is outside Bird’s documented Verify channel plan. |
| Telegram (US) Per message Destination: US | €0.012 EUR Message cost for the selected United States destination. Verification charges are separate. as published | There's no plan, seat, or platform fee for Bird Verify. Channel sends are billed separately. Check the live channel rates below. |
| Viber (US) Per message Destination: US | €0.007 EUR Message cost for the selected United States destination. Verification charges are separate. as published | There's no plan, seat, or platform fee for Bird Verify. Channel sends are billed separately. Check the live channel rates below. This method is outside Bird’s documented Verify channel plan. |
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; carrier fees.
| Destination | Sender type | Per SMS segment |
|---|---|---|
| US | long_code | EUR 0.003 |
| US | long_code | USD 0.0035 |
| US | toll_free | EUR 0.003 |
| US | toll_free | USD 0.0035 |
| US | short_code | EUR 0.006 |
| US | short_code | USD 0.007 |
Bird email pricing and Bird WhatsApp pricing publish the other delivery channels.
How do you start a verification?
Prelude's Node SDK takes a typed target object and code size option. Bird's create endpoint takes the recipient object and optional code length directly.
const response = await fetch("https://api.prelude.dev/v2/verification", {
method: "POST",
headers: {
Authorization: `Bearer ${process.env.PRELUDE_API_TOKEN}`,
"Content-Type": "application/json",
},
body: JSON.stringify({
target: { type: "phone_number", value: "+15551234567" },
options: { code_size: 6 },
}),
});
const verification = await response.json();
console.log(verification.id, verification.status);
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 },
},
)
.safe();
if (error) console.error(error.message);
else console.log(data.id, data.status);
What must change before cutover?
Audit the delivery channels, fraud risk branches, custom templates, sender IDs, and transaction-bound checks your app uses today. Follow the Prelude migration guide to map create and check calls, and plan an alternative if your flow depends on voice calls, RCS, Viber, Zalo, or silent network authentication.
Send new verification requests through Bird while routing in-flight code checks to whichever provider issued the passcode until older sessions expire. Update your webhook signature verifier, persist verified check outcomes in your database, and review Bird's sender and message templates before full cutover.
What should you check before choosing?
Is Bird a Prelude alternative for SMS and email?
Does a retry start a new Prelude verification?
Can I adjust Prelude’s fallback limit on each retry?
What should I store after a successful check?
Where to go next
Start with the migration guide, then compare supported channels and billing units.
- Migrate Verify from PreludeMap create and check fields, risk decisions, and delivery webhooks before moving your flow.
- Bird vs Twilio VerifyCompare recipient-addressed verification, attempt feedback, and channel fallback against Twilio Verify.
- Verify comparisonsCompare verification APIs across channel coverage, retry safety, and fallback rules.
- Verify pricingReview Bird's per-send billing model and published country delivery rates.
- Bird for AI agentsRun verification and channel operations through Bird's authenticated hosted MCP server.
Make verification part of your product.
Talk through your channels, verification flow, and expected traffic with our team.