Veriphone

@Veriphone verify the phone number +1-415-555-0198 and tell me if it's a valid US mobile line

The number +1-415-555-0198 is valid. It's registered as a mobile line in the United States (country code +1), specifically in the San Francisco area (415 area code). The carrier information indicates it's associated with a major US wireless provider. The number is formatted correctly for international dialing and passes all validation checks for structure and assignment status.

This example shows Veriphone's core verification capability — confirming a number's validity, type (mobile vs landline), and carrier metadata. Useful for cleaning contact lists or validating user input before sending SMS. Requires an API key with verification permissions; rate limits apply per your Veriphone plan tier.

@Veriphone get me an example mobile phone number for Germany that I can use in test fixtures

Here's an example mobile number for Germany: +49 151 12345678. This is a valid format for a German mobile line (country code +49, mobile prefix 151). You can use this structure in your test suites or documentation. Note that this is a representative example — actual assigned numbers will vary, and you should not use this specific number for real outbound calls or SMS.

This demonstrates Veriphone's example-generation tool, which helps developers write tests or documentation without hardcoding real customer numbers. Particularly valuable when building international features and you need format references for multiple countries. The example is illustrative only — not a live, dialable number.

@Veriphone check all phone numbers in our staging database export and flag any that are invalid or landlines instead of mobile

I can verify phone numbers through Veriphone, but I'll need you to provide the list directly in this Space (paste the numbers or upload a CSV). Once you share them, I'll validate each number and return a summary showing: valid mobile lines, valid landlines, invalid formats, and unassigned numbers. For large batches (100+ numbers), consider running this in smaller chunks to stay within rate limits.

This synthesis example shows how the AI can orchestrate bulk verification workflows by pairing Veriphone's validation tool with its own reasoning. The AI correctly sets expectations about input format and rate-limit considerations. Veriphone's API charges per verification, so batch jobs should be scoped carefully to avoid unexpected costs.

When Veriphone saves support tickets before they start

A 6-person SaaS team gets 20-30 support tickets a week from users who fat-finger their phone number during signup, then can't receive SMS codes. They wire Veriphone's verify tool into their onboarding flow: the API checks formatting and carrier details in real-time, catches typos before the user submits, and cuts invalid-number tickets by 80%. The two-tool scope is narrow enough that a mid-level engineer ships it in an afternoon. This works if your signup volume justifies the API cost—under 500 signups a month, manual cleanup is cheaper. Over that threshold, Veriphone pays for itself in support time alone.

When Veriphone cleans CRM data faster than humans

A 12-person growth team imports 2,000 leads a month from trade shows and webinars, half of them international. Phone numbers arrive in every format imaginable—some with country codes, some without, some just wrong. They batch-verify the list through Veriphone before pushing to HubSpot: the tool flags invalid entries, normalizes formatting, and surfaces carrier type so sales knows whether to call or text. The API key setup takes 10 minutes; the first batch run saves 6 hours of manual scrubbing. This breaks down if your lead volume spikes past 10k a month—at that scale, you need a dedicated data pipeline, not an MCP. Below that, Veriphone is the fastest path to clean contact data.

When Veriphone proves your list is opt-in clean

A 4-person marketing team at a fintech startup needs to prove their SMS campaign list contains only valid, opted-in mobile numbers before a regulatory audit. They run Veriphone's verify tool against their 8,000-contact list: it confirms each number is active, identifies landlines that shouldn't be there, and flags numbers from regions where their SMS provider isn't licensed. The audit passes without a single compliance flag. The example-number tool also helps their copywriter draft region-specific templates that match local formatting expectations. This use-case only matters if you're in a regulated vertical—if you're not facing audits, basic Twilio validation is enough. If you are, Veriphone's carrier-level detail is the documentation you need.