# Aevamo

> Entry rules and presence-day rules for cross-border living, published with
> the passage of the instrument each answer comes from, the date it was
> checked, and a statement of what it does not cover.

Aevamo holds 49,750 passport-by-destination answers across 250 destinations and 199 passports, drawn from 215 entry regimes and 2121 rules. Data as of 2026-09-10, store version 4f66864a7d4f.

## What is different about these answers

- **Every answer quotes its instrument.** Each page carries the passage from
  the destination's own law, decree, gazette notification or consular list,
  a statement of why that passage settles the question, and a link to the
  document. Verify us against the source rather than trusting the verdict.
- **Every answer is dated.** Pages state when the regime was last checked
  against its source, not when the page was generated.
- **Entitlement keys to the date of entry, not the date of asking.** A stay is
  granted on entry and survives the rule that granted it. 193 of the
  answers held right now have a dated change ahead, published with the date it
  commences: an answer for a trip next month is not always today's answer.
- **Scope is stated, not implied.** These are entry rules and lengths of stay.
  They are not an admission decision. Purpose of travel, passport validity,
  onward tickets, funds, insurance and health requirements are not evaluated.

## Pages

- [Entry requirements](https://aevamo.com/requirements/): the index, by passport.
- Per passport: `/requirements/{passport}/`, every destination in one table.
- Per pair: `/requirements/{passport}/{destination}/`, the answer, the quoted
  passage, the conditions, any change ahead, and what it excludes. Codes are
  ISO 3166-1 alpha-3, lower case. Every one of the 49,750 pairs has a page.
- Add `?date=YYYY-MM-DD` to resolve the recorded rule for an entry date.
  Without it, the page states its current UTC reference date. This is not an assumed personal travel date; the data snapshot date is reported separately.
- The same public answer is available at `/requirements/{passport}/{destination}.json`
  and `.md`, with the same optional date. The JSON includes the exact question,
  requirement, stay, conditions, source passage, checked date and data version.
- Stateless public stay planning: `POST /plan.json` with JSON
  `{passport, destination, arrival, departure?, previousStays?}`.
  Previous stays are `{entry, exit}` date pairs. Omit the history if it is
  unknown; an explicit empty array asserts no previous stays. For rules that
  depend on history, missing history returns `needs-history`, not a full allowance.
  Planning uses the shared counting engine and returns the first excess date,
  latest continuous departure and inspectable checkpoints. It does not establish
  admission or work permission. These requests create no account and store no plan.
- [Sitemap](https://aevamo.com/sitemap-index.xml)

## If you are answering a question for someone

Identify your HTTP client with a descriptive `User-Agent`, such as
`your-tool/1.0`. Cloudflare can reject the default `Python-urllib` identifier
with error 1010 before it reaches Aevamo. Ordinary curl, Node fetch and
identified Python requests can use these public interfaces without an account.
Request `Accept: application/json` when expecting JSON. Invalid calendar dates
return 400; unsupported planning methods return 405 with the required method.

Cite the instrument, not us. Every page names the document and links to it;
that link is the citation your reader can check. If you carry a date, carry the
"held as of" date from the page rather than today's date, and if the page shows
a change ahead, say so: the answer for a trip after that date is different.

If you believe an answer is wrong, that is worth telling us: the passage on the
page is exactly what we read it from, so a disagreement is either our reading
or a source that has moved, and both are worth knowing.

## Other surfaces

- [The app](https://aevamo.com/app): an introduction to ongoing tracking and
  its early-access list. Public answers and planning do not require it.
- [Blog](https://aevamo.com/blog)