Voi
Voi Technology is a Stockholm-based shared micromobility operator founded in August 2018 by Fredrik Hjelm, Adam Jafer, Filip Lindvall, and Douglas Stark. The company runs Europe's largest shared e-scooter and e-bike fleet, with 150,000+ vehicles deployed across 110+ towns and cities in 13 European countries, serving 8+ million riders who have completed 400+ million trips. Voi has been EBIT-profitable since 2024 and in 2026 unveiled a refreshed vehicle family including a new e-scooter model and two upgraded e-bikes, with first deployments in Stockholm. Voi exposes a public Partner API surface (MaaS Light and MaaS Pro) and standards-based open mobility feeds — GBFS v2/v3 for vehicle locations and system information, and MDS 0.4 for trips, status changes, and events — used by cities and MaaS aggregators across Europe. The Partner API also covers user registration, rental lifecycle (start/end), vehicle and zone discovery, pricing, payments, deeplinks, asset access, and customer support flows. Voi additionally publishes a GitHub organization (github.com/voiapp) hosting partner API docs, an iOS networking layer, a VIPER framework, an MDS fork, and internal tooling.
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 Voi the way a machine reads it — 3 machine-readable artifacts across 2 APIs, 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 — Voi scores 16.8/100 (emerging), with a separate agent-readiness read of 0/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 Voi
Each block below is one kind of artifact we hold for Voi. 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 2
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.
Voi MaaS Light API
Voi's read-only open mobility API surface, exposing GBFS v2/v3 auto-discovery, system information, free bike status (with optional battery extension), and service areas, plus MD...
Voi MaaS Pro API
Voi's commercial Partner API enabling MaaS partners to embed full ride journeys in their apps — register users, start and end rentals, look up active and historical rentals for ...
Security Posture 1
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 Voi — 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 1
Portal, sign-up, and the first successful call
Documentation 1
Reference material describing how the API behaves
Build 2
SDKs, sample code, and the tooling you integrate with
Access & Security 1
Authentication, authorization, and security posture
Learn 1
Tutorials, courses, talks, and written guidance
Operate 2
Status, limits, changes, and where to get help
Commercial 2
Pricing, plans, and the legal terms of use
Company 9
The organization behind the API
Scroll within the panel for all 9 ·
Other 1
Properties that don't map to a standard resource type
← All providers · Data indexed from github.com/api-evangelist/voi-app · machine-readable index on apis.io