Geo / SIM Verification
See what a real local SIM in Latin America sees: price, currency, availability.
- 1 corridor, 2 monitored targets (expected vs observed)
- 800 checks / month
- 1 GB evidence storage
- 10,000 API requests / month
- 60-day retention
The problem
Geo-fencing and per-country feature flags fail silently, with no visibility from the real network/SIM context of the end user.
Who it is for
Any company with prices, content, or availability that vary by market and wants to see what a real local SIM in Latin America observes.
What you send us
| Field | Format | Validation |
|---|---|---|
| url | http(s) URL | No literal IP, no control characters, SSRF denylist |
| price_selector / currency_selector / cta_selector / availability_selector | CSS selector, max 300 chars | Length + control-character check only — never reaches a device shell |
| expected_language | BCP-47 code | Free text, length-capped |
| expected_currency | ISO-4217 code | 3-letter alphabetic pattern |
| country_code | 2-letter code | Required; must be one of your plan’s included corridors |
| contexts | Array of country/corridor strings | Compared pairwise; count capped by the plan's included corridors — not checked against a specific authorized-corridor list |
What runs
- The worker loads the URL from each declared context (SIM/network combination) and compares content, price, currency, availability, CTA and language across contexts — always disclosing whether the context was Wi-Fi, roaming or a local SIM.
- Each check compares the expected context against what one real local SIM in Latin America observes.
What you get
- One MonitorRun per comparison
- Screenshots
- Evidence
- Dashboard/API per plan
Limits & quotas
Loading...
Autonomy
Runs unattended per declared context.
Compliance
Results always declare the real network/SIM context observed — WiFi, roaming, or a local SIM is never hidden. Each check compares the context you expect (language, currency, price, availability) against what one real local SIM in Latin America observes; it is not a multi-country comparison. The SIM country is stated at checkout, before payment, and recorded in every signed run.
Evidence
Known limitations
- Each check compares your expected context against what one real local SIM in Latin America observes — not two countries side by side.
- This is not a multi-country comparison. The country of the SIM is stated at checkout, before payment, and recorded in every signed run.
- Runs from a real phone with a real SIM in the served corridor; today the browsing path is the phone's Wi-Fi (the site sees a local fixed-line ISP address, not a mobile-carrier address); the network path is recorded in every signed run.