OneBusAway
OneBusAway is an open-source real-time transit information platform managed by the Open Transit Software Foundation. It provides transit riders with real-time arrival predictions, service alerts, and schedule data for buses, trains, and other transit modes. The platform exposes a RESTful API that lets developers access agency information, stop data, route details, trip information, real-time arrivals and departures, vehicle positions, and service alerts. Authentication uses an API key passed as a query parameter. The reference deployment runs at api.pugetsound.onebusaway.org; many transit agencies host their own OneBusAway instances using the same API contract. Official SDKs are published for Go, Java, Kotlin, JavaScript/Node.js, Python, and Ruby, all generated from a shared OpenAPI 3.0 specification in the sdk-config repository.
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 OneBusAway the way a machine reads it — 99 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 — OneBusAway scores 46.5/100 (developing), 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
How this is scored →scored 2026-07-27 · rubric v0.5
How we profile OneBusAway
Each block below is one kind of artifact we hold for OneBusAway. 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.
OneBusAway default API
The default API from OneBusAway — 13 operation(s) for default.
OneBusAway Where API
The Where API from OneBusAway — 17 operation(s) for where.
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 six things the Kin Score reads for commercial clarity.
Published pricing tiers and plan structures.
Semantic 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.
context Context
JSON-LDSpectral Rules 1
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.
OneBusAway API Rules
SPECTRALJSON Schema 61
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.
Agency
JSON SCHEMAAgencyResponse
JSON SCHEMAArrivalDepartureForStop
JSON SCHEMAArrivalDepartureForStopResponse
JSON SCHEMAArrivalsDeparturesForLocationResponse
JSON SCHEMAArrivalsDeparturesForStopResponse
JSON SCHEMABlockConfiguration
JSON SCHEMABlockEntry
JSON SCHEMABlockResponse
JSON SCHEMABlockStopTime
JSON SCHEMABlockTrip
JSON SCHEMAConfig
JSON SCHEMAConfigResponse
JSON SCHEMACoverage
JSON SCHEMACoverageResponse
JSON SCHEMACurrentTime
JSON SCHEMACurrentTimeResponse
JSON SCHEMADetailedScheduleStopTime
JSON SCHEMALocation
JSON SCHEMAPolylines
JSON SCHEMAReference
JSON SCHEMAResponseWrapper
JSON SCHEMARoute
JSON SCHEMARouteIDsForAgencyResponse
JSON SCHEMARouteResponse
JSON SCHEMARoutesForAgencyResponse
JSON SCHEMARoutesForLocationResponse
JSON SCHEMAScheduleEntry
JSON SCHEMAScheduleForRouteResponse
JSON SCHEMAScheduleForStopEntry
JSON SCHEMAScheduleForStopResponse
JSON SCHEMAScheduleFrequency
JSON SCHEMAScheduleStopTime
JSON SCHEMASearchRouteResponse
JSON SCHEMASearchStopResponse
JSON SCHEMAShapeResponse
JSON SCHEMASituation
JSON SCHEMAStop
JSON SCHEMAStopGrouping
JSON SCHEMAStopIDsForAgencyResponse
JSON SCHEMAStopResponse
JSON SCHEMAStopRouteDirectionSchedule
JSON SCHEMAStopRouteSchedule
JSON SCHEMAStopTime
JSON SCHEMAStopTripGrouping
JSON SCHEMAStopsForAgencyResponse
JSON SCHEMAStopsForLocationResponse
JSON SCHEMAStopsForRouteResponse
JSON SCHEMATimeWindow
JSON SCHEMATrip
JSON SCHEMATripDetails
JSON SCHEMATripDetailsResponse
JSON SCHEMATripEntry
JSON SCHEMATripResponse
JSON SCHEMATripSchedule
JSON SCHEMATripStatus
JSON SCHEMATripVehicleResponse
JSON SCHEMATripWithStopTimes
JSON SCHEMATripsForLocationResponse
JSON SCHEMAVehicleStatus
JSON SCHEMAVehiclesForAgencyResponse
JSON SCHEMAScroll within the panel for all 61 ·
Examples 30
Real request and response payloads are what turn a spec from abstract into obvious — and they're one of the twelve things an agent needs to call an API correctly on the first try.
Example request and response payloads for these APIs.
Get_Api_Where_Config.Json
EXAMPLEReportproblemwithstop
EXAMPLEReportproblemwithtrip
EXAMPLESearchroute
EXAMPLESearchstop
EXAMPLEScroll within the panel for all 30 ·
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.
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 OneBusAway — 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 3
Reference material describing how the API behaves
Agent Surfaces 1
MCP servers, agent skills, and machine-readable catalogs
Build 14
SDKs, sample code, and the tooling you integrate with
Scroll within the panel for all 14 ·
Access & Security 2
Authentication, authorization, and security posture
Commercial 1
Pricing, plans, and the legal terms of use
Company 1
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/onebusaway · machine-readable index on apis.io