For developers and AI agents

Try a sourced answer.

Passport, destination, entry date.

Get the rule, source and checked date.

No key needed for the demo.

Building on Aevamo? Try a free pilot.

REST: get an answer

OpenAPI: JSON (opens in a new tab) · YAML (opens in a new tab) · Discovery (opens in a new tab)

curl 'https://api.aevamo.com/v1/entry/check?passport=GBR&destination=PRT&date=2026-11-01'
Scroll code ↔
More REST requests

GET /v1/entry/requirements

Uses the same query fields.

Both entry routes accept POST JSON.

For stays, POST to /v1/stay/check:

{"passport":"GBR","destination":"PRT","date":"2026-11-01","trips":[]}
Scroll code ↔

Empty trips means no previous stays.

See OpenAPI for days left and trips.

It also documents rules and sources.

Read status, conditions and scope.

Missing coverage still returns 200:

status: "unknown"

MCP: ask from an agent

Streamable HTTP:

https://api.aevamo.com/mcp (opens in a new tab)

No install. Send POST JSON-RPC.

Initialize and ask 
# Initialize
curl 'https://api.aevamo.com/mcp' \
  -H 'Content-Type: application/json' \
  -d '{"jsonrpc":"2.0","id":1,"method":"initialize","params":{"protocolVersion":"2025-03-26","capabilities":{},"clientInfo":{"name":"my-tool","version":"1.0"}}}'

# Ask a dated question
curl 'https://api.aevamo.com/mcp' \
  -H 'Content-Type: application/json' \
  -d '{"jsonrpc":"2.0","id":2,"method":"tools/call","params":{"name":"entry_check","arguments":{"passport":"GBR","destination":"PRT","date":"2026-11-01"}}}'
Scroll code ↔
Tools and results

tools/list discovers available tools:

Entry, stay, trip, rule and source.

Answer calls return:

result.structuredContent

Plus a sourced text summary.

Check result.isError before use.

Public answer formats

Dated answer · JSON · Markdown

Use lower-case ISO alpha-3 codes.

Set the entry date: ?date=YYYY-MM-DD

Routes and citations

llms.txt explains scope and citations.

It also documents routes and dates.

Website and API formats differ.

Use each format's matching contract.

Limits and access

Demo defaults:

100 answer requests per UTC day per IP.

REST and MCP tools/call share it.

Resets at midnight UTC.

Rate limits and errors

REST quota headers:

RateLimit-Limit

RateLimit-Remaining

RateLimit-Reset

Quota exhausted: HTTP 429.

demo_quota_exhausted

Retry-After gives the wait.

MCP puts that error in its tool result.

Key header:

Authorization: Bearer <key>

Valid-key defaults:

120 requests per burst; 40 per second.

Also unlocks the bulk snapshot.

Every request has an IP flood guard:

60 requests per burst; 20 per second.

Operators can override defaults.

Discovery (opens in a new tab) shows current settings.

Website crawl limit, per IP:

Over 20 answers in 10 seconds:

Blocked for 10 seconds.

Need a key?

[email protected]

Send your use case and volume.

Agree usage rights with support.

Prices and commitments are agreed.

Check API health

API health (opens in a new tab) checks database availability.

It also reports the data version.

It is not an incident history.

It is not a service guarantee.

Attribution and licence

Credit Aevamo. Link to its dated answer.

The API is proprietary. Read the terms.

Agree production rights with support.

Source and usage requirements

Retain the official source link.

Keep the passage and checked date.

Keep the data version and caveats.

Separate interpretation from source.

The demo grants no commercial rights:

Embedding, caching or redistribution.

Agree those before production use.

Entry and stay rules aid planning.

Answers do not establish admission.

Nor work or residence rights.

Nor a tax position.

Versions and deprecation

Breaking changes get a new path: /v2.

Aevamo-Version: contract revision.

Aevamo-Data-Version: rules snapshot.

Also in the answer's dataVersion.

Deprecation and Sunset headers:

At least 12 months between them.