Ecosystem · generate, convert, consume

Roadbook integrations

Roadbook is an open JSON interchange format for complete travel itineraries. Anything that writes or reads a .roadbook.json file is an integration. This page lists what exists today and what is planned — planned items are clearly marked and should not be relied upon yet.

status legend available in preparation planned / example

Generate#

Any tool that can emit JSON can produce a Roadbook. No registration, API key or permission is required.

IntegrationStatusNotes
AI assistantsChatGPT, Claude, Gemini, Perplexity, local models: the prompt builder produces a tailored prompt; the assistant generates the file from the public spec and schema. Workflow →
scriptsBuild the object, serialize to JSON, validate with roadbook-validate.mjs or the JSON Schema. See examples for the shape of each feature.
official player — conversational builderThe official player roadbook.plus ships an AI assistant that creates and edits trips from a conversation and exports .roadbook.json.
structured output (AI APIs)Use the JSON Schema as the response schema, then run the validator for integrity rules.
travel planners / agency back-officesAny planner can export Roadbook. None is listed yet — submit yours.

Convert#

Importers turning existing material into Roadbook. None of these converters exists as an official tool today; they are listed as natural targets, and the format already has the fields to receive their output.

SourceStatusMaps to
e-mail confirmationsbookings (refs, payment, check-in/out, tickets with real payloads), transport details for flights and trains.
PDF itineraries / vouchersdays + items, bookings, tickets.voucher (kept as a URL), people for guides and drivers.
calendar (iCalendar)Events → items with time/endTime, locations → place; the reverse export (Roadbook → iCal) is a common player feature.
booking / OTA exportsbookings with structured transport, rooms, payment.payer for corporate travel.
GPX / KML routesroute.km, day coords, item coords; the track itself stays a separate file.

Building one of these? The spec and examples show the target shape; validate your output and tell us so it can be listed here.

Consume#

IntegrationStatusNotes
roadbook.plus — official playerroadbook.plus: offline-first PWA: today / trip / tickets / info, per-traveler links and roles, scannable tickets, surprise mode, plan B, sync, import/export. Details →
validator — web / CLI / ESM / HTTPvalidator.html (local, nothing uploaded), node cli.mjs file, import { validateRoadbook } from 'roadbook-validate.mjs'. Errors copyable as an AI repair prompt.
minimal rendererroadbook-view.mjs — read-only HTML rendering, MIT, a starting point for your own viewer.
compatible third-party viewersNone listed yet. Submit yours; requirements in compatibility.

Developer tooling#

ToolStatusNotes
JSON Schemaroadbook.schema.json, draft 2020-12. Usage →
@roadbookformat/validate (npm)Package in preparation, wrapping the reference validator and the schema with zero dependencies: import { validateRoadbook } from '@roadbookformat/validate'. Not published yet — use the ESM file directly meanwhile.
GitHub repositoryA public repository (spec, schema, validator, examples, tests) is being prepared. Until it is published, this site is the canonical distribution.
Python helperPossible later (roadbook-format). Meanwhile validate with jsonschema against the schema — snippet.
testsAll examples validate against the schema and the reference validator; internal links, sitemap and llms.txt URLs are checked.

Agents#

ToolStatusNotes
llms.txt / llms-full.txtConcise index and self-contained summary of the format for AI crawlers and agents.
MCP serverPlanned: create / validate / repair tools reusing the reference validator, implemented on the official player side. Design note →
HTTP validation APIPOST https://roadbookformat.org/api/validate (or GET ?url=) — the reference validator for agents that can only make HTTP calls; stateless, CORS open. Local validation stays the primary path. Docs →