Web/Mobile Assurance

Geo / SIM Verification

See what a real local SIM in Latin America sees: price, currency, availability.

  • geo_compare
Available
$89.00/mo
  • 1 corridor, 2 monitored targets (expected vs observed)
  • 800 checks / month
  • 1 GB evidence storage
  • 10,000 API requests / month
  • 60-day retention
Start now
01 — The problem

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.

02 — What you send us

What you send us

FieldFormatValidation
urlhttp(s) URLNo literal IP, no control characters, SSRF denylist
price_selector / currency_selector / cta_selector / availability_selectorCSS selector, max 300 charsLength + control-character check only — never reaches a device shell
expected_languageBCP-47 codeFree text, length-capped
expected_currencyISO-4217 code3-letter alphabetic pattern
country_code2-letter codeRequired; must be one of your plan’s included corridors
contextsArray of country/corridor stringsCompared pairwise; count capped by the plan's included corridors — not checked against a specific authorized-corridor list
03 — What runs

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.
04 — What you get

What you get

json
{
  "status": "ok",
  "detail_json": { "context": "local-sim", "price_observed": "19.90", "currency_observed": "USD", "availability_observed": true },
  "screenshot_path": "evidence/2026-09-23/geo-sim/run_1f7c.png",
  "failure_class": null,
  "recovery_actions_json": null,
  "evidence_signature_json": {
    "signature": "44e1...b7",
    "algorithm": "Ed25519",
    "key_id": "witnio-run-ed25519-2026-09"
  },
  "ran_at": "2026-09-23T14:02:11Z"
}
  • One MonitorRun per comparison
  • Screenshots
  • Evidence
  • Dashboard/API per plan
05 — Limits & quotas

Limits & quotas

Loading...

06 — Autonomy

Autonomy

Runs unattended per declared context.

07 — Compliance

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.

08 — Known limitations

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.
09 — FAQ
FAQ

Questions about this service

No. Each check shows what one real local SIM in Latin America observes; it is not a multi-country comparison. The country of the SIM is stated at checkout, before payment, and recorded in every signed evidence record.

Ready for Geo / SIM Verification?