Transparency · Visa data

How we keep visa data accurate, without scraping or expensive APIs

Visa rules change unpredictably. Most consumer-facing planners parrot a single source, when it's wrong, every traveller it touches gets wrong information. JetlyGo cross-checks every rule against multiple independent public datasets, surfaces the confidence level on every answer, and re-verifies weekly. Here's exactly how.

37,294
Total rules in DB
31,906
Cross-verified (2+ sources)
0
Manually verified (high)
25,374
Hand-curated (medium)

Our sources

Every rule in our database cites a source URL. We currently combine four independent inputs and use a cross-source agreement signal to decide what to show end users.

Passport Index dataset

MIT License

Community-maintained dataset of every passport × every destination pair, updated quarterly. Provides our base coverage of 199 passports across 199 destinations (~39,000 rules). Used to initially seed every rule at low confidence, only promoted to visible when a second source agrees.

Source: github.com/imorte/passport-index-data

Wikipedia visa-requirements articles

CC BY-SA 4.0

“Visa requirements for [nationality] citizens” pages are continuously maintained by volunteer editors and cite primary government sources (Timatic, embassy publications, IATA). We parse the structured tables and use them to confirm or contest our other sources. When Wikipedia and the Passport Index agree, the rule becomes visible. When they disagree, we mark it disputed.

Attribution as required by CC BY-SA 4.0: rule data parsed from Wikipedia articles is licensed under Creative Commons Attribution-ShareAlike 4.0 International. Specific article URLs are stored on every affected rule and shown in the “source” field of the visa checker UI.

Example articles: Indian, US, UK citizens.

UK Foreign, Commonwealth & Development Office

Open Government Licence v3.0

UK gov.uk publishes travel advice for 226 destinations with a machine-readable last-updated timestamp. We use these timestamps as a freshness signal: when their advice for a country updates, our corresponding rules get flagged for re-verification, even if our other sources haven't noticed yet.

Source: gov.uk Content API , content is © Crown copyright, licensed under OGL v3.0.

Hand-curated rules

Our editorial review

For the most frequently-checked nationalities (initially Indian passport holders, expanding over time), we manually review each rule against the destination's official immigration website or embassy publication. Curated rules sit at medium confidence by default; the owner promotes individual rules to high confidence via the internal review tool after personally verifying.

Tracking surface (owner-only): /admin/visa-review

How we verify

Confidence levels

Every rule carries a confidence tag. Only rules at high, medium, or disputed confidence are shown to end users, or low rules where two independent sources agree. Anything weaker stays hidden until a human reviews it.

  • High, Manually verified against the destination's official immigration website by JetlyGo's team within the last 90 days.
  • Medium, Hand-curated from official sources but pending manual re-verification, OR multiple public datasets agree.
  • Disputed, Two sources disagree. The UI shows the conflict so the user knows to double-check the embassy before booking.
  • Low, Single source without independent confirmation. Hidden from users unless a second source corroborates.
  • Unverified, Imported but not yet checked. Never shown to users.

Weekly re-checks

A Cloudflare cron job runs every Monday at 03:00 UTC. It refetches the official source URL for a rotating slice of rules, hashes the visible content, and compares to the snapshot from last week. Any page that changed flags its rule for human re-verification within 24 hours. UK gov.uk travel-advice update timestamps are checked the same way.

When sources disagree

We never silently pick a winner. If our Passport Index dataset says a destination is visa-free for an Indian passport but the Wikipedia article says embassy-visa-required, the rule is marked disputed, both versions are surfaced, and the user sees a “sources disagree, verify with the embassy” warning.

What we don't do

  • No scraping behind paywalls. All sources are either public APIs (gov.uk), permissively-licensed datasets (imorte, MIT), or CC-licensed Wikipedia content. We do not bypass anyone's Terms of Service.
  • No commercial visa API. Sherpa, IATA Timatic, and similar services start at $0.05 per query, costs that we'd inevitably need to pass on to travellers. By relying on public sources we keep the visa checker free for everyone forever.
  • No invented data. Every rule cites a real URL we can show you. If a rule has no verifiable source, it doesn't appear.

⚠️ Important disclaimer

Always verify with the destination's embassy or official immigration website before booking travel. Visa policies can change overnight, even our weekly re-check can miss same-day announcements. JetlyGo's visa data is provided for planning convenience, not legal advice. We are not an immigration adviser, embassy, or government agency.

If you spot a rule you believe is incorrect, please email hello@jetlygo.com with the source URL, we typically update within 24 hours.