Need help with your APIs? I offer API discovery, governance & evangelism services. Explore services →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC
Moovit website screenshot

Moovit

Moovit is a Tel Aviv-founded urban mobility company acquired by Intel in May 2020 for approximately $900M and now part of Mobileye's Mobility-as-a- Service (MaaS) business. The Moovit consumer app provides public transit trip planning, real-time arrivals, and service alerts to more than 1.5 billion users across 3,500+ cities in 112+ countries, sourcing both official agency data and crowdsourced transit reports from its global community. Moovit's commercial offering is the Public Transit API suite — a thin, volume-metered HTTP API exposing six API families (Trip Plan, Nearby, Stops, Lines, Real-Time, Service Alerts) plus GTFS-Realtime feeds and a search API. The APIs power Microsoft (Azure Maps), Uber, Lyft, Cubic, and city/transit-agency MaaS deployments. Authentication is HMAC-SHA256 with a metro-scoped request header (USER_LOC or MOOVIT_METRO_ID). Pricing and rate limits are negotiated per customer; there is no self-service developer signup — credentials are issued by [email protected].

agent aware

Limited machine-readable signal and partial portal coverage — documentation a human can read, but little a machine or agent can consume without scraping.

Kin Score

API Evangelist profiles Moovit the way a machine reads it — 29 machine-readable artifacts across 9 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 — Moovit scores 34.7/100 (thin), with a separate agent-readiness read of 41/100 (agent aware). 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 Kin Score How this is scored →
scored 2026-07-27 · rubric v0.5
Composite quality — 34.7/100 · thin
Contract Quality 12.8 / 25
Developer Ergonomics 7.0 / 20
Commercial Clarity 4.2 / 20
Operational Transparency 0.7 / 13
Governance 0.0 / 12
Discoverability 10.0 / 10
Agent readiness — 41/100 · agent aware
Machine-Readable Contract 18 / 18
Agentic Access Contract 15 / 15
MCP Server 0 / 12
Machine-Readable Auth 10 / 10
Idempotency 0 / 9
Stable Error Semantics 0 / 8
Request/Response Examples 0 / 7
Rate-Limit Signaling 0 / 7
Typed Event Surface 0 / 6
Agent Skills 0 / 5
Well-Known Catalog 0 / 4
Consent & Bot Identity 0 / 3

How we profile Moovit

Each block below is one kind of artifact we hold for Moovit. 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 9

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.

Moovit General API

Metro agencies and supported transit types.

Moovit GTFSRealtime API

GTFS-RT feeds for vehicles, trip updates, and service alerts.

Moovit Lines API

Line metadata, stops, geometry, schedules, and alerts.

Moovit Nearby API

Locate stops, bikes, and scooters near a coordinate.

Moovit RealTime API

Live arrival predictions for stops and lines.

Moovit Search API

Search stops and lines by name or number.

Moovit ServiceAlerts API

Metro service alerts and details.

Moovit Stops API

Stop metadata, lines served, reviews, and photos.

Moovit TripPlan API

Multimodal trip planning and itinerary details.

Scroll within the panel for all 9 ·

Open Collections 1

Open, tool-agnostic collections carry the same runnable value as Postman without locking you to one client — the portable, forkable form of the same exercise.

Open, tool-agnostic API collections (OpenAPI-derived and Bruno).

Features 16

The notable capabilities this provider advertises, captured as structured features so they can be searched and compared instead of read one landing page at a time.

Notable capabilities this provider offers.

Multimodal trip-planning API with seamless A-to-B routing across walk, transit, bike, and scooter
Real-time arrivals with single-stop, multi-stop, and multi-stop-with-alerts batch queries
Service alerts API (per-line, per-metro, and individual alert detail)
Stops API — basic info, lines served, reviews, photos, and aggregated details
Lines API — metadata, stops, shape, pattern shape, schedule, alerts, reviews, and full info
Nearby API — locate stops, bikes, and scooters within 5km
GTFS-Realtime feeds (vehicle/trip-updates RT, service-alerts RT, polygon-restricted RT)
Search API for stops and lines
HMAC-SHA256 authentication with API_KEY and nonce/timestamp signing
Metro-scoped requests via USER_LOC (lat, lon) or MOOVIT_METRO_ID header
Thin, low-latency response surface engineered for high-volume consumer apps
Volume-metered commercial pricing with negotiated tiers (no self-service)
3,500+ cities, 112+ countries, 1.5B+ users covered by Moovit's data graph
Crowdsourced transit data layered onto official agency feeds
Customers include Microsoft (Azure Maps), Uber, Lyft, Cubic, and city/transit-agency MaaS deployments
Directions Widget (web embed) and Deeplinking (mobile) integration options for non-API consumers

Scroll within the panel for all 16 ·

Security Posture 2

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.

Moovit Authentication

apiKey · 2 schemes

SECURITY

Moovit Domain Security

TLSv1.3 · HSTS · DMARC

SECURITY

Agentic Access 1

An x-agentic-access contract marks which operations are safe for an agent to run on its own and which need a human in the loop. It is the difference between an API an agent can use and one it can use safely.

Recommended x-agentic-access execution contracts for AI agents.

Moovit Agentic Access

34 operations

34 operations · 0 acting

AGENTIC

Resources

Every other property we hold for Moovit — 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 2

Reference material describing how the API behaves

Agent Surfaces 1

MCP servers, agent skills, and machine-readable catalogs

Build 1

SDKs, sample code, and the tooling you integrate with

Access & Security 2

Authentication, authorization, and security posture

Learn 1

Tutorials, courses, talks, and written guidance

Commercial 2

Pricing, plans, and the legal terms of use

← All providers · Data indexed from github.com/api-evangelist/moovit · machine-readable index on apis.io