Open Mobility Foundation
The Open Mobility Foundation (OMF) is a city-governed, open source foundation that stewards open data standards such as the Mobility Data Specification (MDS) and the Curb Data Specification (CDS), used by cities and their technology partners to manage shared mobility (scooters, bike share, car share, taxis, TNCs, AVs, delivery robots) and digitize public space and curbs. It brings together public and private sector stakeholders to develop the standards, OpenAPI definitions and tools for the public right-of-way.
Real signal across most facets with visible, nameable gaps — the contract exists but is thin, or the portal is good while governance and commercial terms are absent.
API Evangelist profiles Open Mobility Foundation the way a machine reads it — 44 machine-readable artifacts across 6 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 — Open Mobility Foundation scores 41.6/100 (developing), with a separate agent-readiness read of 29/100 (agent ready). 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. Every facet and dimension name is a link: it opens that measurement's page on APIs.io, where the rating runs across the whole catalog — the exact checks that feed it, how every profiled provider distributes on it, and who is at the top of it.
Kin Score
How this is scored →scored 2026-10-17 · rubric v0.24.0
Put this on your own site. The badge is drawn live from Open Mobility Foundation's current Kin Score — paste it once and it updates itself every time the score is recomputed. It follows your visitor's light or dark setting, and it links back here so anyone who sees it can read the full breakdown.
<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/open-mobility-foundation/"
title="Open Mobility Foundation on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/open-mobility-foundation.svg"
alt="Open Mobility Foundation Kin Score — API readiness rating by API Evangelist" width="150" height="150" loading="lazy">
</a>[](https://providers.apievangelist.com/providers/open-mobility-foundation/)<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/open-mobility-foundation/"
title="Open Mobility Foundation on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/open-mobility-foundation/card.svg"
alt="Open Mobility Foundation Kin Score — API readiness rating by API Evangelist" width="340" height="120" loading="lazy">
</a>More shapes, themes and sizes → · Score as JSON · How badges work
How we profile Open Mobility Foundation
Each block below is one kind of artifact we hold for Open Mobility Foundation. 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 15
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.
Open Mobility Foundation Events API
The Events API from Open Mobility Foundation — 3 operation(s) for events.
Open Mobility Foundation Geographies API
The Geographies API from Open Mobility Foundation — 2 operation(s) for geographies.
Open Mobility Foundation Geographies.json API
The Geographies.json API from Open Mobility Foundation — 1 operation(s) for geographies.json.
Open Mobility Foundation Jurisdictions API
The Jurisdictions API from Open Mobility Foundation — 2 operation(s) for jurisdictions.
Open Mobility Foundation Jurisdictions.json API
The Jurisdictions.json API from Open Mobility Foundation — 1 operation(s) for jurisdictions.json.
Open Mobility Foundation Metrics API
The Metrics API from Open Mobility Foundation — 1 operation(s) for metrics.
Open Mobility Foundation Policies API
The Policies API from Open Mobility Foundation — 2 operation(s) for policies.
Open Mobility Foundation Policies.json API
The Policies.json API from Open Mobility Foundation — 1 operation(s) for policies.json.
Open Mobility Foundation Reports API
The Reports API from Open Mobility Foundation — 2 operation(s) for reports.
Open Mobility Foundation Requirements API
The Requirements API from Open Mobility Foundation — 1 operation(s) for requirements.
Open Mobility Foundation Stops API
The Stops API from Open Mobility Foundation — 2 operation(s) for stops.
Open Mobility Foundation Telemetry API
The Telemetry API from Open Mobility Foundation — 1 operation(s) for telemetry.
Open Mobility Foundation Trips API
The Trips API from Open Mobility Foundation — 1 operation(s) for trips.
Open Mobility Foundation Value API
The Value API from Open Mobility Foundation — 1 operation(s) for value.
Open Mobility Foundation Vehicles API
The Vehicles API from Open Mobility Foundation — 4 operation(s) for vehicles.
Scroll within the panel for all 15 ·
Pricing Plans 1
Pricing is part of the interface. Machine-readable plans tell you what a tier costs and includes before you commit — one of the things the Kin Score reads for access clarity — renamed from commercial clarity in rubric 0.12, because a free statutory interface has access terms and no commercial ones.
Published pricing tiers and plan structures.
Rate Limits 1
Rate limits are the difference between a demo that works and a production integration that doesn't fall over. Publishing them is an operational-transparency signal — and a hard requirement for any agent that plans its own throughput.
Documented rate limits and quota policies.
Open Mobility Foundation Rate Limits
RATE LIMITSSemantic Vocabularies 1
JSON-LD contexts give the data shared meaning across APIs. We profile them because semantics are what let a machine reconcile 'customer' here with 'customer' somewhere else.
JSON-LD contexts and semantic vocabularies used across these APIs.
Spectral Rules 2
Governance rulesets we run against this provider's specs — the automated checks behind parts of the score. Profiling them makes the quality bar explicit and re-runnable, not a matter of opinion.
JSON Schema 20
Standalone JSON Schema definitions describe the data models behind the API. We profile them so the shapes are validatable on their own — useful long after a single request is forgotten.
Standalone JSON Schema definitions for this provider's data models.
column
JSON SCHEMAdata-types/iso-dayhourminute
JSON SCHEMAdata-types/iso-duration
JSON SCHEMAdata-types/timestamp
JSON SCHEMAdata-types/uuid
JSON SCHEMAmodels/event
JSON SCHEMAmodels/geography
JSON SCHEMAmodels/jurisdiction
JSON SCHEMAmeasures
JSON SCHEMAmodels/mutable-stop
JSON SCHEMAmodels/policy
JSON SCHEMAquery
JSON SCHEMAmodels/report
JSON SCHEMAmodels/requirements
JSON SCHEMAresponse/last_updated
JSON SCHEMAresponse/version
JSON SCHEMAmodels/stop
JSON SCHEMAmodels/telemetry
JSON SCHEMAmodels/trip
JSON SCHEMAmodels/vehicle
JSON SCHEMAScroll within the panel for all 20 ·
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.
Scopes 1
OAuth scopes are the vocabulary of least-privilege access. Profiling them shows exactly what an integration — or an agent acting on a user's behalf — is allowed to do.
OAuth scopes governing access to this provider's APIs.
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.
Resources
Every other property we hold for Open Mobility Foundation — 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.
Documentation 1
Reference material describing how the API behaves
Agent Surfaces 2
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 10
Pagination, idempotency, versioning, errors, and events
Scroll within the panel for all 10 ·
Build 1
SDKs, sample code, and the tooling you integrate with
Access & Security 3
Authentication, authorization, and security posture
Operate 3
Status, limits, changes, and where to get help
Commercial 2
Pricing, plans, and the legal terms of use
Company 3
The organization behind the API
Other 3
Properties that don't map to a standard resource type
← All providers · Data indexed from github.com/api-evangelist/open-mobility-foundation · machine-readable index on apis.io
This is an independent, third-party profile of Open Mobility Foundation, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.
The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.
Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.
info@apievangelist.com
·
Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and
you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.