Hivemapper
Hivemapper (Bee Maps) is a decentralized mapping network that turns a planetary-scale fleet of purpose-built "Bee" dashcams into fresh, structured, queryable street-level data. Contributors passively collect imagery while driving and earn HONEY tokens on Solana; the data is processed through on-device and cloud ML pipelines and delivered to developers as REST APIs. The Bee Maps Developer API offers a Street-Level Imagery API, a Map Features API (ML-detected signs, hydrants, lane lines and more), an AI Event Videos API (harsh braking, swerving, violations with synchronized sensor data), and Burst on-demand mapping, plus Edge AI for deploying custom ML workloads to cameras. Enterprise customers include HERE Technologies, Lyft, Mapbox, and Volkswagen. Billing is consumption-based (API credits plus per-view metering).
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 Hivemapper the way a machine reads it — 8 machine-readable artifacts across 5 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 — Hivemapper scores 49.9/100 (developing), with a separate agent-readiness read of 38/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 Hivemapper
Each block below is one kind of artifact we hold for Hivemapper. 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 5
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.
Hivemapper Account API
Devices, calibration, and query history.
Hivemapper AI Events API
AI-detected driving event videos with synchronized sensor data.
Hivemapper Bursts API
On-demand incentivized mapping requests.
Hivemapper Imagery API
Street-level dashcam imagery queries.
Hivemapper Map Features API
ML-detected road objects and features.
MCP Servers 1
Model Context Protocol servers expose these APIs directly to AI agents. We profile them because agent-native access is the fastest-growing way this provider's capabilities actually get used.
Model Context Protocol servers that expose these APIs to AI agents.
hivemapper-mcp.yml
MCP SERVERSecurity 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.
Resources
Every other property we hold for Hivemapper — 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 4
Portal, sign-up, and the first successful call
Documentation 2
Reference material describing how the API behaves
Agent Surfaces 4
MCP servers, agent skills, and machine-readable catalogs
Build 4
SDKs, sample code, and the tooling you integrate with
Access & Security 1
Authentication, authorization, and security posture
Operate 2
Status, limits, changes, and where to get help
Commercial 3
Pricing, plans, and the legal terms of use
Company 3
The organization behind the API
Other 1
Properties that don't map to a standard resource type
← All providers · Data indexed from github.com/api-evangelist/hivemapper · machine-readable index on apis.io