Limited free access
Free access stays small: one pull per crossing every four hours, current wait, and basic metadata. It does not include broad history, CSV, resale, webhooks, or branding controls.
Agent Connect
Planned access for assistants, MCP clients, and publishing tools that need border wait data with visible attribution and clear limits.
Quick answer
Agent Connect exists to answer one practical traveler need: what data is used, what action is available, and where to check before driving.
Agent Pro
Agent Pro is planned for higher limits, public history within plan limits, nearby data, widget tools, and ad/coupon/SEO drafts for review.
Supported clients
First version will target generic MCP clients, search assistants, AI desktops, editors, and publishing flows that can preserve attribution.
Public API
Public read endpoints remain the base: current wait, allowed history, nearby crossings, catalog, site configuration, and widgets with canonical links.
View feedsAgent catalog
The JSON catalog publishes source contracts for read tools, limits, attribution, client profiles, and MCP status without expanding private runtime.
View JSON catalogOpenAPI
The OpenAPI output lists public feeds, widgets, and Agent Connect discovery. Private implementation surfaces stay excluded.
OpenAPI JSONAttribution required
Every answer, widget, or integration must keep site name, canonical link, source, timestamp, and freshness context. Old data must not be presented as current.
AI policySafe scope
Agents should use public data only and, when authenticated, the vendor's own data. Private areas, payments, accounts, write routes, and other vendors' data stay out of scope.
Security