Core page fields
Every route includes path, page kind, title, summary, description, confidence note, source counts, and a metadata object for treatment, destination, price posture, trip length, recovery window, and related routes.
One route contract for the site, the API, and any downstream tooling.
The frontend reads the same page records exposed by the backend. That keeps the public HTML routes, directory cards, and any future internal tooling on one normalized treatment-destination model.
Why `metadata` exists
The directory needs structured route facts. Without a typed metadata block, the frontend would have to guess treatment and destination attributes from prose.
Source packet fields
When a source sync completes, the page record now carries the latest extracted source title, summary, final URL, HTTP status, and content-change timestamp for each attached source.
Entry matrix
Page records now include a normalized entry matrix with traveler-profile presets, explicit country-selector context options, access type, ETA state, stay windows, passport-validity rules, visa options, source links, and traveler-document stacks.
Partner offers
Route records now include normalized partner-offer cards with headline, disclosure, placement, redirect tracking key, and destination URL so the frontend can drive users toward live clinic paths without hardcoded links.
Current state
The entry matrix is seeded for the current destination set and now supports preset traveler profiles, direct passport-country selectors, Mexico and Turkey residence-country overrides, and India departure-country overrides for a first official-source yellow-fever-risk set. Route records also expose normalized partner offers and destination/regulator source layers. Other residence and itinerary combinations remain partial until they are seeded from destination authority guidance.
Endpoints
Public URLs
These are the routes currently exposed by the backend worker.
List page inventory https://api.procedureatlas.com/api/v1/pages Returns the route directory used by the homepage, including metadata for treatment, destination, and planning facts. Resolve a route by path https://api.procedureatlas.com/api/v1/pages/by-path?path=/procedures/dental-implants/mexico Returns the full route record used by the catch-all treatment page template, including traveler-profile entry requirements. Filter a route by traveler profile https://api.procedureatlas.com/api/v1/pages/by-path?path=/procedures/ivf/spain&traveler_profile=us_passport_ordinary Returns the same route record but narrows the normalized entry matrix to one traveler profile or document stack. Filter a route by passport country https://api.procedureatlas.com/api/v1/pages/by-path?path=/procedures/knee-replacement/india&passport_country=NZ Returns the route record with entry rules matched through explicit passport-country selectors instead of only a preset traveler profile. List traveler profiles https://api.procedureatlas.com/api/v1/traveler-profiles Returns the supported traveler profiles used by the normalized entry-rule matrix, including document-stack profiles. OpenAPI document https://api.procedureatlas.com/openapi.json Machine-readable contract for the public API. MCP endpoint https://api.procedureatlas.com/mcp POST-only JSON-RPC surface for agents or tools that need the same route inventory.