Lanes & Planes
Lanes & Planes is a Munich-based travel and expense (T&E) management platform that positions itself as the financial infrastructure for European corporate travel. The platform covers the full T&E lifecycle in one system: travel request, digital approval flows, booking, and final accounting. Its inventory spans European rail (Deutsche Bahn, ÖBB, SBB, SNCF), flights from the major global carriers and alliances including NDC content, over seven million hotels via direct interfaces plus HRS, Expedia and Booking.com, Airbnb for Work, global rental cars, and ground mobility including the Deutschland-Ticket and Flixbus. The product is built for finance departments, emphasizing VAT-compliant automated invoicing, German per-diem (VMA) tax logic, centralized billing on a single creditor, real-time budget tracking, and automated travel-policy enforcement. It integrates with ERP and accounting systems (DATEV, SAP, Microsoft Dynamics, Sage, Addison) and with HRIS platforms, offering native Personio synchronization and an External API (ExtAPI) for other HRIS and identity systems such as Workday, BambooHR and HiBob. Enterprise authentication is via SAML 2.0 single sign-on. The company is certified to ISO 27001 and ISO 9001, is GDPR compliant, and hosts on European servers. Lanes & Planes is backed by Battery Ventures.
More than an index entry, but the surface is still mostly links rather than artifacts — the cohort most likely to move a full band from modest, well-targeted work.
API Evangelist profiles Lanes & Planes the way a machine reads it — 4 machine-readable artifacts across 1 API, pulled from the provider's own public surface and indexed so a developer, an analyst, or an AI agent can evaluate it against every other provider on the network.
Every provider in the network is reduced to the same set of machine-readable artifacts — OpenAPI contracts, event specifications, GraphQL schemas, runnable collections, pricing and rate-limit signals, security posture, OAuth scopes, and the agent surfaces (MCP servers and skills) that let software drive the API on its own. We profile them because the interface is the part of a company you can actually inspect: it is a truer signal of what a provider does than any marketing page. From those artifacts we compute the Kin Score — Lanes & Planes scores 26.6/100 (emerging), with a separate agent-readiness read of 10/100 (human only). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.
Kin Score
This is the API Evangelist rating — a single, repeatable read computed from the artifacts on this page. Green fill is points earned; the red track is points possible, so every bar shows earned-versus-possible at a glance.
Kin Score
How this is scored →scored 2026-07-27 · rubric v0.5
How we profile Lanes & Planes
Each block below is one kind of artifact we hold for Lanes & Planes. For each we say what it is and why it earns a place in the profile, then list every one we've indexed — capped at two rows, scroll within the panel for the rest.
APIs 1
Each API is captured as its own OpenAPI definition — every operation, parameter, and response. This is the single most useful machine-readable description of what an API does, and it's what lets us score, lint, mock, and generate against it without asking the provider for anything.
Individual APIs this provider publishes, each with its own machine-readable definition.
Lanes & Planes External API (ExtAPI)
The External API (ExtAPI) is named in the company's own llms.txt as the integration surface used to synchronize employee and organizational data from HRIS and identity systems t...
Security Posture 3
Authentication, domain security, vulnerability disclosure, and trust-center signals — the evidence that a provider takes security seriously enough to document it. We profile it because you can't govern what you can't see.
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Resources
Every other property we hold for Lanes & Planes — documentation, portals, status pages, policies, and corporate surface — grouped by the job it does, following the integrator's arc from getting started to running in production.
Get Started 2
Portal, sign-up, and the first successful call
Documentation 1
Reference material describing how the API behaves
Agent Surfaces 1
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 1
Pagination, idempotency, versioning, errors, and events
Access & Security 5
Authentication, authorization, and security posture
Operate 2
Status, limits, changes, and where to get help
Commercial 3
Pricing, plans, and the legal terms of use
Company 6
The organization behind the API
Other 2
Properties that don't map to a standard resource type
← All providers · Data indexed from github.com/api-evangelist/lanes-and-planes · machine-readable index on apis.io