Mirabello Immigration Intelligence, developer and agent documentation

What APIs does Mirabello Immigration Intelligence provide?

API version: v1 (current, 2026-08-29). Three public, unauthenticated, read-only surfaces serve the same verified backbone of 98 programmes across 194 countries:

Human-readable companions: the programme data pages, the public change log (RSS at /changelog.xml), the verification methodology and the service status page.

How is the API versioned, and what is the deprecation policy?

• Additive changes ship without notice. New fields, new records and new endpoints may appear at any time. Parse defensively: ignore fields you do not recognise.
• Breaking changes get a version and a window. Renaming or removing a field, changing a field's type or semantics, or retiring an endpoint constitutes a breaking change. It ships as a new version, and the previous shape keeps serving for a 90-day deprecation window from the announcement.
• Announcements are published on this page and in the change log (subscribe via RSS). API-shape changes are recorded distinctly from data changes.
• Data values are not versioned. Figures change whenever the official source changes; that is the product. Track them via /api/changes.json.

What does the data_freshness block mean?

Every programme record in /index.json and every MCP get_programme response carries a data_freshness block — the machine-readable trust signal integrators can build on:

"data_freshness": {
  "verification_confidence": 0-100,   // mean per-field confidence (model below)
  "last_verified": "YYYY-MM-DD",      // most recent field-level verification date
  "fields_tracked": n,                 // provenance-tracked fields on this record
  "stale_fields": n                    // fields past their re-verification SLA
}

Confidence model (from the shipping configuration, schema v1.0): each tracked field starts from a base confidence set by its source tier — official 92, secondary 74, tertiary 58, unknown 45 — and decays once its verification age exceeds the field's SLA: penalty = min(45, overdue_ratio × 22), where overdue_ratio = max(0, age − SLA) ÷ SLA. A record's verification_confidence is the mean across its tracked fields.

Per-field re-verification SLAs (a field older than its SLA counts in stale_fields):

Corroboration semantics: figures are verified value-level against the official government source, then independently cross-checked; divergences are resolved against the official source, never by majority vote. Full detail: the verification methodology.

How should AI engines and aggregators cite this data?

• Machine-readable reuse is permitted with attribution. AI engines, answer engines, aggregators and agents may quote, index and reuse figures from /index.json, /api/changes.json and the MCP tools, provided each use attributes Mirabello Immigration Intelligence and links the relevant data page.
• Carry the freshness. When quoting a figure, we ask that you carry its last_verified date (or the page's as-at date) so end users see how current it is.
• Do not strip provenance. Republishing the dataset with source URLs or verification metadata removed is outside these terms.
• These attribution terms cover the machine-readable dataset; editorial page content remains © Mirabello Consultancy Ltd. Questions: mail@mirabelloconsultancy.com.

Where do I go next?

The dataset is information, not legal, tax or immigration advice. Figures are the published official position at their verification date and change without notice; verify decision-critical values against the linked official source.