Phone Carrier Compatibility Checker & BYOD Tool avatar

Phone Carrier Compatibility Checker & BYOD Tool

Pricing

$10.00 / 1,000 results

Go to Apify Store
Phone Carrier Compatibility Checker & BYOD Tool

Phone Carrier Compatibility Checker & BYOD Tool

Check whether an unlocked, imported, or travel phone will work on a carrier using official evidence across 30 markets and 80 carriers. Built for BYOD, activation, resale, bulk checks for 1 to 100 phones, automation, and AI agents; returns UNKNOWN instead of guessing when evidence is insufficient.

Pricing

$10.00 / 1,000 results

Rating

0.0

(0)

Developer

Liou

Liou

Maintained by Community

Actor stats

0

Bookmarked

1

Total users

1

Monthly active users

21 days ago

Last modified

Share

Will my phone work on this carrier? This phone compatibility checker covers 30 markets and 80 carriers using official carrier evidence. It targets BYOD compatibility, unlocked phone compatibility, international phone compatibility, imported phone compatibility, and travel phone compatibility. No guessing from generic band lists: when evidence is insufficient, it fails closed.

Quick start

Enter just four required fields:

  • Phone brand - for example, Apple or Samsung.
  • Phone model - for example, iPhone 15 or Galaxy S25.
  • Use in country - where you want to use the phone.
  • Carrier to use - the mobile network you plan to use.

Run the Actor. Each phone returns a human-readable status, summary, and next_step, plus stable machine fields for APIs and AI agents.

CARRIER_CONFIRMED means the reviewed official evidence supports the scoped carrier conclusion. CARRIER_CONFIRMATION_REQUIRED is a normal, useful result- not an error: the official evidence was found, but the carrier still requires its own confirmation step. UNKNOWN means the evidence is insufficient, unavailable, blocked, or has changed, so the Actor fails closed instead of guessing.

Optional regional/hardware variant and eight-digit tac can make a check more specific. Full IMEI is never accepted. For bulk phone compatibility, add additional_queries with up to 99 extra phones for 1 to 100 checks per run.

Phone carrier compatibility checker for BYOD and unlocked phones

Use it before switching carriers, activating an unlocked phone, taking an international phone abroad, checking an imported device, preparing travel, resale, provisioning, or automating compatibility decisions in an API or AI-agent workflow.

Current official-source coverage

MarketCarriersVerification
AustraliaOptus, TPG, Telstra, VodafoneOptus: manual official check; TPG: official source; Telstra: official source; Vodafone: official source
AustriaA1, MagentaA1: manual official check; Magenta: official source
BelgiumOrange, ProximusOrange: official source; Proximus: official source
BrazilClaro, TIM, VivoClaro: manual official check; TIM: manual official check; Vivo: manual official check
CanadaBell, Rogers, TELUS, Virgin PlusBell: official source; Rogers: official source; TELUS: manual official check; Virgin Plus: official source
FranceBouygues Telecom, Orange, SFRBouygues Telecom: official source; Orange: official source; SFR: official source
GermanyDeutsche Telekom, O2, VodafoneDeutsche Telekom: manual official check; O2: official source; Vodafone: official source
Hong KongChina Mobile HK, cslChina Mobile HK: manual official check; csl: official source
IndiaAirtel, Jio, ViAirtel: official source; Jio: official source; Vi: official source
IndonesiaIM3, TelkomselIM3: manual official check; Telkomsel: official source
ItalyVodafone, WINDTREVodafone: official source; WINDTRE: manual official check
JapanNTT docomo, Rakuten Mobile, SoftBank, auNTT docomo: official source; Rakuten Mobile: official source; SoftBank: official source; au: official source
MalaysiaCelcomDigi, Maxis, U MobileCelcomDigi: official source; Maxis: official source; U Mobile: official source
MexicoMovistar, TelcelMovistar: official source; Telcel: manual official check
NetherlandsKPN, OdidoKPN: official source; Odido: official source
New Zealand2degrees, One NZ2degrees: official source; One NZ: official source
PhilippinesGlobe, SmartGlobe: manual official check; Smart: official source
PolandOrange, Plus, T-MobileOrange: manual official check; Plus: official source; T-Mobile: manual official check
PortugalMEO, NOS, VodafoneMEO: official source; NOS: official source; Vodafone: official source
Saudi ArabiaMobily, stcMobily: official source; stc: official source
SingaporeM1, SIMBA, Singtel, StarHubM1: official source; SIMBA: manual official check; Singtel: official source; StarHub: official source
South AfricaMTN, VodacomMTN: official source; Vodacom: official source
South KoreaKT, SK TelecomKT: official source; SK Telecom: official source
SpainOrange, VodafoneOrange: official source; Vodafone: manual official check
SwitzerlandSalt, Sunrise, SwisscomSalt: official source; Sunrise: official source; Swisscom: official source
TaiwanChunghwa Telecom, Taiwan MobileChunghwa Telecom: official source; Taiwan Mobile: official source
ThailandAIS, True-dtacAIS: official source; True-dtac: official source
United Arab Emiratesdudu: official source
United KingdomEE, O2, Three, VodafoneEE: official source; O2: official source; Three: official source; Vodafone: official source
United StatesAT&T, Google Fi, T-Mobile, Tello, VerizonAT&T: official source; Google Fi: official source; T-Mobile: manual official check; Tello: manual official check; Verizon: official source

Coverage expands only when a fixed official source can be safely verified and fixture-tested. An unregistered carrier cannot receive a positive compatibility claim. The product does not claim universal phone compatibility.

Machine-readable coverage: global-phone-compatibility-checker coverage --json.

Reading the result

Each dataset item starts with three human-readable fields: status gives the plain-language outcome, summary explains what the official evidence supports, and next_step tells you what to do next when another carrier check is required. verdict remains the canonical machine decision for APIs and AI agents.

CARRIER_CONFIRMED means the returned official evidence supports that scoped carrier conclusion. CARRIER_CONFIRMATION_REQUIRED means the carrier still requires its own confirmation step. UNKNOWN means the available evidence is insufficient, unsupported, conflicting, or unavailable.

SOURCE_UNAVAILABLE means a registered official source could not be safely retrieved or verified during the run. The Actor keeps the result truthful—normally UNKNOWN—instead of retrying until it finds a favorable answer.

Feature findings such as VoLTE, VoWiFi, 4G, or LTE are scoped evidence and are not a universal compatibility verdict. A policy requirement alone does not prove that a specific phone supports that feature on that carrier.

Common uses

  • Check whether an unlocked phone can be used before switching carriers.
  • Check an international or imported phone before travel, resale, or activation.
  • Add evidence-backed BYOD compatibility to onboarding and provisioning workflows.
  • Let an API client, automation, or AI agent retrieve a stable result plus official evidence.
  • Identify when an official carrier confirmation step is still required.

FAQ

Will my phone work with my carrier

Enter the phone brand, model, country, and carrier. If the carrier is registered, the Actor evaluates its official evidence and returns a scoped verdict. If evidence is missing or the source has drifted, it fails closed instead of guessing.

Check an unlocked or international phone

Yes. The same contract can be used for unlocked, imported, and international phones. A carrier may still require its own eligibility or device-confirmation step.

IMEI checker boundary

No. This Actor intentionally does not accept a full IMEI. An optional TAC is limited to exactly eight ASCII digits. When a carrier requires a full IMEI, the result can tell you that carrier confirmation is still needed without collecting the identifier here.

AI agents and APIs

Yes. The Actor has stable input/output schemas and returns human-readable status, summary, and next_step fields alongside verdict, confidence, checked_at, features, evidence, source_urls, and confirmation_steps, making it suitable for Apify API, MCP discovery, automation, and agent workflows.