Add travel entry requirements to your app
Travel Entry Requirements returns what a destination asks of a visitor's passport and health documents: how long the passport must stay valid and from when, and whether a yellow fever certificate is required. Paid plans add a passport check against your trip dates, the blank pages it needs, the Schengen 10-year issue rule, the current UK and US travel advisory levels and plain-English guidance for each rule. You switch it on with a single toggle — no SDK and no endpoint wiring — and it answers over MCP or REST using the same key as every other skill.
A real response from the Travel Entry Requirements Skill — exactly what your agent gets back when it makes the call.
{
"destination": "TH"
}Enable Travel Entry Requirements and your app or agent can add travel entry requirements to your app on demand — no SDK, no endpoint wiring. It answers over MCP or REST using the same key as every other skill.
Over MCP, Travel Entry Requirements appears to your model as the entryrequirements tool it invokes whenever a task needs it — you don't write the glue, the agent reaches for it.
Prefer to call it directly? Any language that can send a GET can hit Travel Entry Requirements to add travel entry requirements to your app inline in your own server-side code.
Once enabled, this skill is reachable two ways — pick whichever fits how you build. Both use the same key.
It appears to your model as a callable tool. No extra code — the agent invokes it when a task needs it.
entryrequirementsCall it from your server with one request and your key. Node, Python, Go — anything that can send a GET.
GET /v1/entryrequirementsHow to connect it over MCP or REST.
Same data, same VerveKit account, same credit balance — one key works on all of them.
The same key runs from your first prototype to millions of calls — on APIVerve's rails, 99.9% uptime.
See pricing
