Rome2Rio
Rome2Rio is a multi-modal travel planning platform founded in Melbourne, Australia in 2011, and part of the Omio Group since 2019. It covers 240+ countries, 10 million+ locations, and 20,000+ transport operators, enabling door-to-door route discovery across flights, trains, buses, ferries, and driving. Developers can access route search, geocoding, and autocomplete capabilities through the Rome2Rio REST API, which returns JSON responses covering routes, segments, duration, and operator information for any two points worldwide.
Rome2Rio publishes 3 APIs on the APIs.io network. Tagged areas include Travel, Multi-Modal, Transportation, Routes, and Transit.
The Rome2Rio catalog on APIs.io includes 1 JSON-LD context.
Rome2Rio’s developer surface includes documentation, engineering blog, support, GitHub presence, and 9 more developer resources.
Kin Score
APIs 3
Individual APIs this provider publishes, each with its own machine-readable definition.
Rome2Rio Search API
The Rome2Rio Search API returns multi-modal door-to-door travel routes between any origin and destination worldwide. Given origin and destination as place names or coordinates, ...
Rome2Rio Autocomplete API
The Rome2Rio Autocomplete API provides place-name suggestions as a user types, returning a ranked list of matching locations (cities, airports, train stations, addresses) that c...
Rome2Rio Geocode API
The Rome2Rio Geocode API resolves a place-name or address string to a canonical Rome2Rio place record with geographic coordinates, place type, and country, enabling precise orig...
Pricing Plans 1
Published pricing tiers and plan structures.
Rate Limits 1
Documented rate limits and quota policies.
Rome2Rio Rate Limits
RATE LIMITSFinOps 1
Cost, billing, and metering signals for API financial operations.
Rome2Rio Finops
FINOPSSemantic Vocabularies 1
JSON-LD contexts and semantic vocabularies used across these APIs.
Apis Context
JSON-LDSecurity Posture 1
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Resources
Documentation 1
Reference material describing how the API behaves
Build 1
SDKs, sample code, and the tooling you integrate with
Access & Security 1
Authentication, authorization, and security posture
Operate 2
Status, limits, changes, and where to get help
Commercial 2
Pricing, plans, and the legal terms of use
Company 4
The organization behind the API
Other 2
Properties that don't map to a standard resource type
Source (apis.yml)
Work with this as data
Every provider here is available over the APIs.io API and to AI agents over MCP.
MCP server
One button, every client — Claude, Cursor, VS Code and the rest.
https://apis.io/mcp
Tools for providers
9 MCP tools reach this
find_providersBrowse and filter every provider in the catalog.get_provider_artifactsEvery artifact this provider publishes, grouped by type.get_provider_operationsEvery operation across all of their OpenAPIs — one call instead of parsing every spec.get_provider_toolsEvery MCP tool they ship, with the operation each wraps.get_provider_evidenceHow each part of their score was established. Free — the basis for a claim should not sit behind it.get_provider_ratingPRO — composite, band, trend and facet scores.apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.resolveTurn a domain, URL or GitHub org into the provider it belongs to.find_cohortsEvery scored population of providers in the catalog.
Call it yourself
curl for this page
curl "https://apis.io/api/v1/providers/rome2rio"
curl "https://apis.io/api/v1/providers?limit=25"
curl "https://apis.io/api/v1/providers/rome2rio/operations?limit=25"
curl "https://apis.io/api/v1/providers/rome2rio/evidence"
Discovery needs no key. Ratings and market analysis are Pro.