Hivemapper

• Name: Hivemapper
• URL: https://www.hivemapper.com/
• Category: decentralized geospatial data infrastructure / mapping network / DePIN
• Summary: Hivemapper is a decentralized street-level mapping network and geospatial data control plane. The durable project-layer value is the mapping marketplace itself: contributor hardware, street-level imagery capture, data-product packaging, map credits, HONEY burn-and-mint mechanics, and the way map freshness gets turned into a tokenized network output. The named governance boundary around token economics, open-technology stewardship, hardware certification, and the Bee Maps-versus-foundation split now lives separately in hivemapper-foundation.
• What it does:
  • Coordinates contributors who capture street-level imagery and train map AI models to build and refresh a global map
  • Sells or licenses multiple data products and APIs, including street-level imagery, static and dynamic map features, HD maps, and AI-driver-event data for developers and enterprises
  • Uses HONEY as the network token, rewarding contributors while requiring map-data consumers to burn tokens or otherwise acquire map credits for usage
  • Uses Map Improvement Proposals (MIPs) as the documented path for major changes to network structure, governance, and HONEY token economics
  • Defines open device and mapping-technology standards so contributor hardware and the broader mapping stack are not reduced to one closed dashcam product
• Key claims:
  • The homepage positions Hivemapper as a real-time global street-level mapping network built by people, cameras, and apps rather than as a traditional centralized mapping vendor
  • The app-developer docs show a fairly mature product surface: Beekeeper, street-level image APIs, Scout, static and dynamic map-features APIs, HD maps, and AI-driver-event data
  • The HONEY docs describe a capped supply, a burn-and-mint model, and map-consumption rewards, which makes Hivemapper look more like an onchain data marketplace with contributor incentives than a one-off mapping app
  • The governance docs make the MIP process and foundation split explicit, which is useful project-layer context because rule changes, token economics, and hardware policy are part of the live network design rather than afterthoughts
  • The strongest project-level reason to keep Hivemapper in the corpus is that it packages contributor hardware, AI-assisted labeling, enterprise map-data sales, token incentives, and open-technology claims into one geospatial control plane rather than just another drive to earn app
• Whitepaper: No canonical standalone Hivemapper whitepaper or litepaper surfaced in this pass. The strongest current primary materials are the official docs, governance / MIP materials, tokenomics pages, and adjacent foundation sources; see ../whitepapers/hivemapper-primary-sources-2026-04-27.md and ../whitepapers/hivemapper-foundation-primary-sources-2026-08-11.md.
• Sources:
  • https://www.hivemapper.com/
  • https://docs.hivemapper.com/
  • https://docs.hivemapper.com/welcome/introduction
  • https://docs.hivemapper.com/use-map-data/hivemapper-app-developers
  • https://docs.hivemapper.com/welcome/network-governance
  • https://docs.hivemapper.com/honey-token/what-is-honey
  • https://www.hivemapperfoundation.org/

Internal linkages

• Governance / entity boundary: hivemapper-foundation.

Protocol / company / foundation boundary

• Keep this note on the mapping network itself: contributors, cameras, imagery, data products, map-credit economics, HONEY burn-and-mint behavior, and the broader geospatial-data-marketplace design.
• Use hivemapper-foundation when the sharper question is who stewards token economics, open technologies, hardware certification, and the official MIP rule-change lane.
• That split matters because what does Hivemapper sell and how does the network work? is different from which named entity shapes the governance and token-economic shell around that network?

Control surface

• Hivemapper is not just a map app. The interesting project-layer control surface is the bundle: contributor hardware, data-collection incentives, enterprise-facing API products, map-credit consumption, and the tokenized marketplace that ties them together.

• The strongest live pressure points are freshness incentives, imagery-quality rules, data-product packaging, token burn-and-mint policy, and the device / standards layer that determines who can contribute and how.

• For the named governance entity above those mechanics, read hivemapper-foundation.

• Last reviewed: 2026-08-11 UTC