May Mobility

May Mobility is an American autonomous vehicle technology company headquartered in Ann Arbor, Michigan, founded in 2017 by Edwin Olson, Alisyn Malek and Steve Vozar. It develops and operates self-driving shuttle, microtransit and robotaxi services in partnership with cities, transit agencies, commercial sites and ride-hail networks including Uber and Lyft, using a proprietary Multi-Policy Decision Making (MPDM) autonomy stack. For fleet partners May Mobility publishes a Fleet API at docs.maymobility.com consisting of a Realtime API (WebSocket streaming of vehicle telemetry topics and exterior camera video, the latter as serialized protobuf) and a Batch REST API that returns historical telemetry, LiDAR ROSBAG exports, vehicle shift timings and last-active status. Access is provisioned per account by the Fleet API team and authenticated with AWS Cognito OAuth 2.0 client-credentials tokens. May Mobility also operates its own autonomous system (AS398351) with a public NOC documentation site, peering policy, responsible-disclosure program and internal PKI.

May Mobility publishes 2 APIs on the APIs.io network. Tagged areas include Company, Autonomous Vehicles, Transportation, Mobility, and Robotaxi.

The May Mobility catalog on APIs.io includes 1 event-driven AsyncAPI specification.

May Mobility’s developer surface includes documentation, API reference, getting-started guide, engineering blog, support, authentication, changelog, and 24 more developer resources.

48.3/100 developing ▬ flat Agent 41/100 agent ready Full breakdown ↓
scored 2026-08-05 · rubric v0.9.1
2 APIs
CompanyAutonomous VehiclesTransportationMobilityRobotaxiFleet ManagementTelemetryPublic TransitAutomotiveStreaming

Kin Score

Kin Score Kin Score How this is scored →
scored 2026-08-05 · rubric v0.9.1
Composite quality — 48.3/100 · developing
Contract Quality 12.9 / 25
Developer Ergonomics 11.7 / 20
Commercial Clarity 7.4 / 20
Operational Transparency 7.2 / 13
Governance 0.4 / 12
Discoverability 8.7 / 10
Agent readiness — 41/100 · agent ready
Machine-Readable Contract 18 / 18
Agentic Access Contract 0 / 10
MCP Server 0 / 12
Machine-Readable Auth 10 / 10
Idempotency 0 / 9
Stable Error Semantics 8 / 8
Request/Response Examples 0 / 7
Rate-Limit Signaling 0 / 7
Typed Event Surface 6 / 6
Agent Skills 0 / 5
Well-Known Catalog 4 / 4
Consent & Bot Identity 3 / 3
A2A Agent Card 0 / 8
Dry-Run / Simulate Mode 0 / 4
Improve this rating by publishing the missing artifacts — every area above can be raised, and the full rubric is at apis.io/rating/. This rating is computed from github.com/api-evangelist/may-mobility: open an issue to ask a question, or submit a pull request to add artifacts. Want it done for you? Prioritized profiling — $2,500 →

APIs 2

Individual APIs this provider publishes, each with its own machine-readable definition.

May Mobility Fleet Realtime API

A WebSocket streaming API that delivers live May Mobility vehicle data in two modes. Telemetry mode streams JSON messages for a comma-separated list of per-vehicle topics (GPS, ...

May Mobility Fleet Batch (REST) API

A REST API that returns historical May Mobility vehicle data between two Unix timestamps. Telemetry is retrieved per vehicle and topic at /vehicles/{vehicleID}/topics/{topicName...

Event Specifications 1

AsyncAPI definitions for this provider's event-driven and streaming APIs.

Security Posture 4

Authentication, domain security, vulnerability disclosure, and trust-center signals.

May Mobility Fleet Authentication

oauth2 · 1 scheme

SECURITY

May Mobility Domain Security

TLSv1.3 · HSTS · DNSSEC · DMARC

SECURITY

May Mobility Vulnerability Disclosure

Hackerone · security.txt · contact published

SECURITY

May Mobility Trust Center

trust center published

SECURITY

Scopes 1

OAuth scopes governing access to this provider's APIs.

May Mobility Scopes

OAuth 2.0 · no documented scopes

0 scopes

SCOPES

Resources

Get Started 2

Portal, sign-up, and the first successful call

Documentation 2

Reference material describing how the API behaves

Agent Surfaces 2

MCP servers, agent skills, and machine-readable catalogs

Design & Contract 6

Pagination, idempotency, versioning, errors, and events

Build 3

SDKs, sample code, and the tooling you integrate with

Access & Security 8

Authentication, authorization, and security posture

Scroll for all 8

Operate 3

Status, limits, changes, and where to get help

Commercial 2

Pricing, plans, and the legal terms of use

Company 2

The organization behind the API

Other 1

Properties that don't map to a standard resource type

Source (apis.yml)

apis.yml Raw ↑
aid: may-mobility
name: May Mobility
description: May Mobility is an American autonomous vehicle technology company headquartered in Ann Arbor, Michigan, founded
  in 2017 by Edwin Olson, Alisyn Malek and Steve Vozar. It develops and operates self-driving shuttle, microtransit and robotaxi
  services in partnership with cities, transit agencies, commercial sites and ride-hail networks including Uber and Lyft,
  using a proprietary Multi-Policy Decision Making (MPDM) autonomy stack. For fleet partners May Mobility publishes a Fleet
  API at docs.maymobility.com consisting of a Realtime API (WebSocket streaming of vehicle telemetry topics and exterior camera
  video, the latter as serialized protobuf) and a Batch REST API that returns historical telemetry, LiDAR ROSBAG exports,
  vehicle shift timings and last-active status. Access is provisioned per account by the Fleet API team and authenticated
  with AWS Cognito OAuth 2.0 client-credentials tokens. May Mobility also operates its own autonomous system (AS398351) with
  a public NOC documentation site, peering policy, responsible-disclosure program and internal PKI.
image: https://maymobility.com/apple-touch-icon.png
url: https://raw.githubusercontent.com/api-evangelist/may-mobility/refs/heads/main/apis.yml
x-type: company
x-source: harvest:secondary-market
x-tier: profiled
x-tier-reason: enrichment-pipeline
specificationVersion: '0.20'
created: '2026-08-01'
modified: '2026-08-01'
tags:
- Company
- Autonomous Vehicles
- Transportation
- Mobility
- Robotaxi
- Fleet Management
- Telemetry
- Public Transit
- Automotive
- Streaming
apis:
- aid: may-mobility:fleet-realtime-api
  name: May Mobility Fleet Realtime API
  description: A WebSocket streaming API that delivers live May Mobility vehicle data in two modes. Telemetry mode streams
    JSON messages for a comma-separated list of per-vehicle topics (GPS, POSE, DRIVE_STATUS, RUNLEVEL, COLLISION_NOTIFICATION,
    TRAFFIC_LIGHT and others) using the topic form /.vehicle.{vehicleID}.{topicName}, with a documented ceiling of 20 topics
    per connection. Video mode streams exterior camera feeds for up to four vehicles per connection as serialized protobuf
    (quic_wrapper wrapping May.image_t, mostly VP9). Authentication is an AWS Cognito client-credentials access token passed
    as a token query parameter. Access is provisioned by the May Mobility Fleet API team; the connection domain is issued
    per account and is not published.
  humanURL: https://docs.maymobility.com/docs/intro
  baseURL: https://docs.maymobility.com/docs/fleet-api/connecting-to-fleet-api
  tags:
  - Telemetry
  - Streaming
  - WebSockets
  - Autonomous Vehicles
  - Fleet Management
  properties:
  - type: Documentation
    url: https://docs.maymobility.com/docs/intro
  - type: GettingStarted
    url: https://docs.maymobility.com/docs/fleet-api/connecting-to-fleet-api
  - type: APIReference
    url: https://docs.maymobility.com/docs/fleet-api/types-of-data
  - type: Authentication
    url: authentication/may-mobility-fleet-authentication.yml
  - type: ChangeLog
    url: https://docs.maymobility.com/docs/release-notes/realttime-api
  - type: Webhooks
    url: asyncapi/may-mobility-fleet-events.yml
  - type: Protobuf
    url: grpc/may-mobility-quic-wrapper.proto
- aid: may-mobility:fleet-batch-api
  name: May Mobility Fleet Batch (REST) API
  description: 'A REST API that returns historical May Mobility vehicle data between two Unix timestamps. Telemetry is retrieved
    per vehicle and topic at /vehicles/{vehicleID}/topics/{topicName} with startTime and endTime parameters, paginated in
    30-second pages via an opaque metaToken carried on subsequent requests. Discovery endpoints list available vehicles (/vehicles)
    and the topics available for a vehicle (/vehicles/{vehicleID}/topics). Additional endpoints return LiDAR exports as ROSBAG
    files (/lidar plus a /download step), vehicle shift windows (/shift-timing) and vehicle last-active timestamps (/last-active).
    Documented limits: a maximum 10-minute request window, a 7-day retention window, no current-day data, and 5-day LiDAR
    log retention. Authentication is a bearer AWS Cognito access token issued with a batch-specific scope.'
  humanURL: https://docs.maymobility.com/docs/fleet-api/types-of-data
  baseURL: https://docs.maymobility.com/docs/fleet-api/types-of-data
  tags:
  - Telemetry
  - REST
  - Autonomous Vehicles
  - Fleet Management
  - LiDAR
  properties:
  - type: Documentation
    url: https://docs.maymobility.com/docs/fleet-api/types-of-data
  - type: GettingStarted
    url: https://docs.maymobility.com/docs/fleet-api/connecting-to-fleet-api
  - type: APIReference
    url: https://docs.maymobility.com/docs/fleet-api/topics-channels/gps
  - type: Authentication
    url: authentication/may-mobility-fleet-authentication.yml
  - type: ChangeLog
    url: https://docs.maymobility.com/docs/release-notes/batch-api
  - type: ErrorCatalog
    url: errors/may-mobility-fleet-error-catalog.yml
  - type: DataModel
    url: data-model/may-mobility-fleet-data-model.yml
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com
- FN: APIs.json
  email: info@apis.io
x-enrichment:
  date: '2026-08-01'
  status: enriched
  artifacts_added: 17
  pass: local-v1
common:
- type: Website
  url: https://maymobility.com/
- type: DeveloperPortal
  url: https://docs.maymobility.com/
- type: Documentation
  url: https://docs.maymobility.com/docs/intro
- type: APIReference
  url: https://docs.maymobility.com/docs/fleet-api/types-of-data
- type: GettingStarted
  url: https://docs.maymobility.com/docs/fleet-api/connecting-to-fleet-api
- type: Blog
  url: https://maymobility.com/posts/type/company-blog/
- type: Support
  url: https://maymobility.com/contact/
- type: GitHubOrganization
  url: https://github.com/maymobility
- type: TermsOfService
  url: https://maymobility.com/terms-of-use/
- type: PrivacyPolicy
  url: https://maymobility.com/privacy-policy/
- type: Compliance
  url: https://maymobility.com/cybersecurity/
- type: TrustCenter
  url: security/may-mobility-trust-center.yml
- type: Security
  url: https://net.maymobility.com/docs/policies/security
- type: VulnerabilityDisclosure
  url: security/may-mobility-vulnerability-disclosure.yml
- type: SecurityTxt
  url: well-known/may-mobility-security.txt
- type: WellKnown
  url: well-known/may-mobility-well-known.yml
- type: DomainSecurity
  url: security/may-mobility-domain-security.yml
- type: Authentication
  url: authentication/may-mobility-fleet-authentication.yml
- type: OAuthScopes
  url: scopes/may-mobility-scopes.yml
- type: Conventions
  url: conventions/may-mobility-fleet-conventions.yml
- type: Conformance
  url: conformance/may-mobility-conformance.yml
- type: ErrorCatalog
  url: errors/may-mobility-fleet-error-catalog.yml
- type: Lifecycle
  url: lifecycle/may-mobility-lifecycle.yml
- type: StatusPage
  url: https://status.net.maymobility.com/
- type: ChangeLog
  url: changelog/may-mobility-changelog.yml
- type: DataModel
  url: data-model/may-mobility-fleet-data-model.yml
- type: Packages
  url: packages/may-mobility-packages.yml
- type: SDKs
  url: packages/may-mobility-packages.yml
- type: Protobuf
  url: grpc/may-mobility-quic-wrapper.proto
- type: Webhooks
  url: asyncapi/may-mobility-fleet-events.yml
- type: LLMsTxt
  url: llms/may-mobility-llms.txt