Waze
Waze is a Google-owned, community-driven navigation and real-time traffic application. Its developer surface is not a self-service JSON REST API but a set of public URL-invocation and embed contracts plus partner-gated data and SDK programs. Waze Deep Links open the Waze app from a URL to locate an address, drop a pin, or start turn-by-turn navigation; the Waze iFrame embeds the interactive Live Map in any web page; Waze for Cities Data Feeds let agencies exchange road-closure, incident, and working-vehicle data (CIFS, WZDx, DATEX II, ESRI) and receive a partner-specific JSON alerts feed; the Waze Transport SDK gives transportation apps ETA/routing and trip-data collection; and the Waze Audio Kit surfaces audio content in-drive. Developer documentation is hosted on Google for Developers at developers.google.com/waze and partner programs are provisioned through the Waze Partner Hub.
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 Waze the way a machine reads it — 7 machine-readable artifacts across 4 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 — Waze scores 24.7/100 (emerging), with a separate agent-readiness read of 16/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.
How we profile Waze
Each block below is one kind of artifact we hold for Waze. 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 4
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.
Waze Deep Links
URL-invocation API to open the Waze app from an external link to locate an address, drop a pin, or start navigation. Query params include ll (lat,lon), q (search), navigate, z (...
Waze iFrame (Live Map)
Embeddable client-side component that renders the interactive Waze Live Map inside a web page via an
Waze for Cities Data Feeds
Partner data-exchange for road closures, incidents, and working vehicles using CIFS (preferred), WZDx, DATEX II, or ESRI formats; Waze returns a partner-specific JSON alerts fee...
Waze Transport SDK
Partner-gated SDK for transportation apps to add ETA and routing points and trip-data collection using Waze real-time traffic and location data.
Security Posture 3
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 Waze — 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 1
Reference material describing how the API behaves
Agent Surfaces 2
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 2
Pagination, idempotency, versioning, errors, and events
Access & Security 5
Authentication, authorization, and security posture
Operate 2
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
← All providers · Data indexed from github.com/api-evangelist/waze · machine-readable index on apis.io