Can I enter?

Visas et conditions d'entrée — 199 passeports · 39 402 itinéraires

Can I enter?

Choisissez un passeport et une destination : la règle, le séjour autorisé et ce qu'il faut prévoir avant de partir. Cinq vérifications gratuites par jour, sans compte.

Plus de détails

Ces documents peuvent ouvrir droit à des exemptions lorsque la destination en publie ; à eux seuls, ils ne modifient jamais le verdict de base. Les dates sont vérifiées dans votre navigateur, en fonction du séjour autorisé et de la règle de validité du passeport de la destination : ce que vous saisissez ici n'est utilisé que pour cette vérification et n'est conservé nulle part.

5 vérifications gratuites par jour, sans compte

Vous êtes humain ? Débloquez 20 vérifications par jour

Où aller ensuite · Confiance et transparence · Développeurs et agents : la même vérification, en HTTP

02 — Confiance et transparence

Des chiffres calculés à partir du jeu de données lui-même

Chaque chiffre ci-dessous est calculé à partir du jeu de données effectivement servi par ce déploiement : rien n'est écrit à la main. Chaque règle d'entrée est revérifiée tous les jours auprès de la source officielle citée ; les compteurs en direct viennent directement de la production et sont actualisés toutes les cinq minutes.

199

Passeports couverts

39 402

Itinéraires passeport-destination

191/199

Vérifiées auprès de sources officielles

827

Règles avec source citée

71

Règles revérifiées aujourd'hui

538

Sources officielles contrôlées/j

0d

Ancienneté médiane des vérifications

2026-08-12

Version du jeu de données

Disponibilité de l'API · 30 jours

172/199

Portails officiels de demande de visa référencés

Visites d'agents IA aujourd'hui

Appels d'outils MCP · total

Activité de vérification

  • AGOSources previously flagged unreachable were retried and loaded successfully; live official content matches the stored rules unchanged (prior failures were sandbox/proxy artifacts, not real outages).
  • ARESources previously flagged unreachable were retried and loaded successfully; live official content matches the stored rules unchanged (prior failures were sandbox/proxy artifacts, not real outages).
  • ATGSources previously flagged unreachable were retried and loaded successfully; live official content matches the stored rules unchanged (prior failures were sandbox/proxy artifacts, not real outages).
  • AUSSources previously flagged unreachable were retried and loaded successfully; live official content matches the stored rules unchanged (prior failures were sandbox/proxy artifacts, not real outages).
  • AUTPassport-validity, blank-pages, onward-ticket, residence-permit-exemption and purpose-scope rules re-read against oesterreich.gv.at and bmeia.gv.at, all unchanged; the flagged content-hash change was a cosmetic page-furniture update.
  • BHRSources previously flagged unreachable were retried and loaded successfully; live official content matches the stored rules unchanged (prior failures were sandbox/proxy artifacts, not real outages).
  • BIHSources previously flagged unreachable were retried and loaded successfully; live official content matches the stored rules unchanged (prior failures were sandbox/proxy artifacts, not real outages).
  • BTNPassport-validity, sustainable-development-fee and purpose-scope rules re-read against doi.gov.bt and bhutan.travel, all unchanged.
  • CANPassport, blank-pages, health, TWOV, residence-permit-exemption and purpose-scope rules re-read against canada.ca, all unchanged; the flagged eta.html hash change was a transient scheduled-maintenance banner.
  • CHLFull deep audit: every populated field (passport validity, onward ticket, TWOV, residence-permit exemptions, purpose scope where applicable) re-read against live official sources and found accurate.
  • CHNFull deep audit: every populated field (passport validity, onward ticket, TWOV, residence-permit exemptions, purpose scope where applicable) re-read against live official sources and found accurate.
  • CIVFull deep audit: every populated field (passport validity, onward ticket, TWOV, residence-permit exemptions, purpose scope where applicable) re-read against live official sources and found accurate.
  • CMRFull deep audit: every populated field (passport validity, onward ticket, TWOV, residence-permit exemptions, purpose scope where applicable) re-read against live official sources and found accurate.
  • CODFull deep audit: every populated field (passport validity, onward ticket, TWOV, residence-permit exemptions, purpose scope where applicable) re-read against live official sources and found accurate.
  • COGFull deep audit: every populated field (passport validity, onward ticket, TWOV, residence-permit exemptions, purpose scope where applicable) re-read against live official sources and found accurate.
  • COLSources previously flagged unreachable were retried and loaded successfully; live official content matches the stored rules unchanged (prior failures were sandbox/proxy artifacts, not real outages).
  • COMFull deep audit: every populated field (passport validity, onward ticket, TWOV, residence-permit exemptions, purpose scope where applicable) re-read against live official sources and found accurate.
  • CPVTourist-visa duration corrected from a flat 30-day cap to 90 days (extendable once to 180); transit visa corrected to 4 days; added the EASE pre-registration and TSA airport-tax requirement that applies even to visa-exempt travellers. Passport-validity and onward-ticket reconfirmed unchanged.
  • CRISources previously flagged unreachable were retried and loaded successfully; live official content matches the stored rules unchanged (prior failures were sandbox/proxy artifacts, not real outages).
  • CUBFull deep audit: every populated field (passport validity, onward ticket, TWOV, residence-permit exemptions, purpose scope where applicable) re-read against live official sources and found accurate.
  • CYPDeep audit: blank-pages, airport-transit-visa and two of three residence-permit-exemption clauses reconfirmed unchanged, and the third clause's excluded-country list corrected to 'except the UK and Ireland' (was 'except Ireland'); passport-validity flagged needs_review because the cited embassy page states two different anchors for the 3-month buffer (beyond the visa's validity in one section, beyond the trip in another) without reconciling them.
  • CZEFull deep audit: every populated field (passport validity, onward ticket, TWOV, residence-permit exemptions, purpose scope where applicable) re-read against live official sources and found accurate.
  • DEUFull deep audit: every populated field (passport validity, onward ticket, TWOV, residence-permit exemptions, purpose scope where applicable) re-read against live official sources and found accurate.
  • GABSources previously flagged unreachable were retried and loaded successfully; live official content matches the stored rules unchanged (prior failures were sandbox/proxy artifacts, not real outages).
  • GINSources previously flagged unreachable were retried and loaded successfully; live official content matches the stored rules unchanged (prior failures were sandbox/proxy artifacts, not real outages).
  • HUNSources previously flagged unreachable were retried and loaded successfully; live official content matches the stored rules unchanged (prior failures were sandbox/proxy artifacts, not real outages).
  • INDPassport-validity, blank-pages, onward-ticket and purpose-scope rules re-read against indianembassyusa.gov.in and indianvisaonline.gov.in, all unchanged; the flagged hash change was a page-footer date edit.
  • IRNSources previously flagged unreachable were retried and loaded successfully; live official content matches the stored rules unchanged (prior failures were sandbox/proxy artifacts, not real outages).
  • IRQPassport-validity, blank-pages, onward-ticket and purpose-scope rules re-read against UK FCDO and the Iraqi MOFA, all unchanged.
  • KHMSources previously flagged unreachable were retried and loaded successfully; live official content matches the stored rules unchanged (prior failures were sandbox/proxy artifacts, not real outages).
  • LCAPassport-validity and purpose-scope rules re-read against stlucia.org and govt.lc, unchanged.
  • LSOBlank-pages rule flagged needs_review: the cited source states the 3-clean-pages requirement specifically for trade-purpose visas, while the general embassy visa-requirements list has no blank-pages item at all. Passport-validity, onward-ticket, health and purpose-scope reconfirmed unchanged.
  • MDASources previously flagged unreachable were retried and loaded successfully; live official content matches the stored rules unchanged (prior failures were sandbox/proxy artifacts, not real outages).
  • MNGSources previously flagged unreachable were retried and loaded successfully; live official content matches the stored rules unchanged (prior failures were sandbox/proxy artifacts, not real outages).
  • MOZSources previously flagged unreachable were retried and loaded successfully; live official content matches the stored rules unchanged (prior failures were sandbox/proxy artifacts, not real outages).
  • MUSSources previously flagged unreachable were retried and loaded successfully; live official content matches the stored rules unchanged (prior failures were sandbox/proxy artifacts, not real outages).
  • MYSSources previously flagged unreachable were retried and loaded successfully; live official content matches the stored rules unchanged (prior failures were sandbox/proxy artifacts, not real outages).
  • NAMBlank-pages note corrected: both current MHAISS documents require 3 clean pages uniformly; the prior note's claim of a 2-page exception for online applications was not supported by either source. Passport-validity, onward-ticket, health and purpose-scope reconfirmed unchanged.
  • NGASources previously flagged unreachable were retried and loaded successfully; live official content matches the stored rules unchanged (prior failures were sandbox/proxy artifacts, not real outages).
  • NPLSources previously flagged unreachable were retried and loaded successfully; live official content matches the stored rules unchanged (prior failures were sandbox/proxy artifacts, not real outages).

Données complètes, format machine : GET /transparency · GET /stats.json · GET /changes.json · status.canienter.com

03 — Intégration

La réponse, facturée à la requête.

Un appel non payé renvoie une réponse HTTP 402 accompagnée des instructions de paiement. N'importe quel client x402 règle $0.03 en USDC, puis relance la requête. Les paiements passent par Base mainnet.

# Free tier — 5 checks a day, no auth
curl "https://api.canienter.com/free/check?passport=NLD&destination=JPN"

# Paid tier — answers HTTP 402 Payment Required. The offer (amount,
# asset, pay-to) is base64 JSON in the PAYMENT-REQUIRED header;
# any x402 client settles it and retries automatically.
curl "https://api.canienter.com/v1/check?passport=NLD&destination=JPN"

# Peek at the offer without paying:
curl -s -o /dev/null -D - "https://api.canienter.com/v1/check?passport=NLD&destination=JPN" \
  | grep -i "^payment-required" | cut -d" " -f2 | base64 -d
// npm i @x402/fetch @x402/evm viem   (Node 18+)
// WARNING: running this spends real USDC ($0.03/call, Base mainnet).
// Inspect the offer first, free of charge:
const probe = await fetch("https://api.canienter.com/v1/check?passport=NLD&destination=JPN");
console.log(probe.status, /* 402 */ JSON.parse(atob(probe.headers.get("PAYMENT-REQUIRED"))));

// Then pay per call — key from an env var, never hardcoded or logged:
import { wrapFetchWithPaymentFromConfig } from "@x402/fetch";
import { ExactEvmScheme } from "@x402/evm";
import { privateKeyToAccount } from "viem/accounts";

const account = privateKeyToAccount(process.env.X402_PRIVATE_KEY);
const payFetch = wrapFetchWithPaymentFromConfig(fetch, { schemes: [
  { network: "eip155:8453", client: new ExactEvmScheme(account) }]});

const res = await payFetch(
  "https://api.canienter.com/v1/check?passport=NLD&destination=JPN");
if (!res.ok) throw new Error("check failed: " + res.status);
const { requirement, allowed_stay_days } = await res.json();
# The API publishes its own agent skill (Claude Code paths shown;
# Codex/Cursor/other agents: use your agent's skills directory)
mkdir -p ~/.claude/skills/visa-check
curl -s "https://api.canienter.com/.well-known/agent-skills/visa-check/SKILL.md" \
  -o ~/.claude/skills/visa-check/SKILL.md

# Discovery index with the SKILL.md sha256 digest (verify, updates, extras):
curl -s "https://api.canienter.com/.well-known/agent-skills/index.json"

# Remove: delete ~/.claude/skills/visa-check

La compétence permet à un agent de consulter les conditions d'entrée et de payer à la requête via x402. Aucune clé d'API ne risque donc de fuiter.

Documentation lisible par machine : GET /llms.txt · GET /openapi.json

Ajouter à un agent

EndpointPrix
/free/checkgratuit · 5/jour
/v1/check$0.03
/v1/trips/evaluatemulti-étapes, multi-passeports, explications$0.10
/v1/passport/{iso3}les 198 destinations en une requête$0.15
  • USDC sur Base mainnet · x402 v2
  • Ni compte, ni clé API, ni contrat
  • Chaque réponse indique sa date de mise à jour

01 — Appeler

GET /v1/check : la requête non payée renvoie un HTTP 402 avec une offre de paiement.

02 — Payer

$0.03 USDC via n'importe quel client x402, réglé sur Base mainnet.

03 — Recevoir

JSON verdict, avec le reçu on-chain du paiement.

Vous n'êtes pas développeur ? Les mêmes réponses sur votre site avec deux lignes de HTML : ni appel d'API, ni compte.

04 — Votre site

Fonctionne aussi sur vos pages.

Un guide de voyage, un blog d'expatriation, un tunnel de réservation : collez deux lignes et vos lecteurs voient la condition d'entrée, la durée de séjour autorisée et un lien vers les règles et leurs sources, sans quitter votre page. C'est gratuit pour tous les sites, commerciaux ou non. Seule condition : garder le lien d'attribution visible.

<!-- anywhere in your page -->
<div data-canienter-widget></div>
<script src="https://canienter.com/embed.js" async></script>

<!-- on a Japan guide, pre-select the destination -->
<div data-canienter-widget data-destination="JPN"></div>
  • Ni cookies, ni traçage, ni compte
  • S'adapte au thème clair ou sombre de votre site
  • S'adapte à la largeur disponible
  • Mêmes sources officielles citées

Documentation du widget, options et démo en ligne · Espace développeurs