Visas and entry rules
Entry rules and, where the supplier sells one, a visa application. The routed ids are anc.entry.rules for the check and anc.visa.apply to file.
A requirements result is not a visa. Eligibility is not an approval. This is not legal or immigration advice. Rules change; the supplier response is the record for that call. Routed: anc.entry.rules for the check. anc.visa.apply to file. The price is quoted on the call. This page does not publish a rate card.
Same page for an agent: /use-cases/visas.md
Try it
1. Set your agent up, once
set up Ancilair — https://ancilair.com/llms.txt
2. Ask for the job
Using Ancilair, check entry rules for the nationality, origin, destination, and dates I give you. Read https://ancilair.com/llms.txt. Call anc.entry.rules on https://api.ancilair.com. A requirements result is not a visa. Do not call anc.visa.apply until I say yes to a specific product. This is not legal or immigration advice.
Why this prompt works
- One token. Supplier credentials stay on the server.
- The price is the quote on the call, at the supplier's rate, with 0% markup.
- A contract the team already holds is never metered, and it wins over Ancilair's account.
- A quote, a search, a plan list, or a requirements check is not a booking. The follow-up runs only after an explicit yes, with an Idempotency-Key.
- Timatic and CIBT VisaCheck do not file a visa, so they are not on anc.visa.apply. Sherpa visa products and SimpleVisa applications are the filing tools.
Why go through Ancilair
- One token. Supplier credentials stay on the server.
- The price is quoted on the call, at the supplier's rate, with 0% markup.
- A key the team already holds is never metered, and it wins over Ancilair's account.
- A named supplier is a different tool id, not a new integration.
Suppliers
| Supplier | Tool | What the call needs | Price |
|---|---|---|---|
|
|
sherpa.entry.rules |
Nationality, origin, destination, travel dates. Returns the procedures. Not an application. | Quoted on the call |
sherpa.visa.products |
The same trip, when you need an eVisa or eTA offer and its price. Listing products does not file anything. | Quoted on the call | |
sherpa.visa.apply |
The product the traveller accepted. Idempotency-Key required. Runs only after an explicit yes. | Quoted on the call | |
|
|
simplevisa.requirements |
Nationality, destination, departure date. Returns the documents and whether an authorization is required. Not an application. | Quoted on the call |
simplevisa.visa.apply |
The applicant and the trip, for a destination the requirements call says SimpleVisa can file. Idempotency-Key required. Only after an explicit yes. Runs only after an explicit yes. | Quoted on the call | |
|
|
timatic.entry.check |
Nationality, travel document, destination, travel dates. Returns the compliance result Timatic publishes. Not a visa. | Quoted on the call |
|
|
cibt.visa.check |
Nationality, residency, destination, purpose of travel, entry date, exit date. Not an application. | Quoted on the call |
Sequences that use this job
-
Before they fly
Entry rules, a visa product only if one is required, then an eSIM. Filing waits for a yes.