Maps are one of the most critical pieces of infrastructure for human society and the global economy.

Billions of people around the world use mapping apps every day. Millions of organizations, from businesses to government agencies, rely on mapping APIs and services to support their operations. With every year that passes, more and more of the world's 1.5 billion vehicles use advanced technology features that demand richer map data than ever before.

Analysts estimate the mapping industry has a market size of $200B to $300B, including mapping apps and APIs, geospatial analytics, GIS, and map data collection.

But there's a problem.

Most of today's maps are built by deploying dedicated vehicles to collect high-quality, street-level imagery. That's expensive, so mapmaking is consolidated among the few companies with the capital to map roads at global scale. It means maps often don't reflect current realities on the ground.

And yet, most roads are driven every day. In the United States alone, humans drove 3.26 trillion miles in 2022, or 8.9 billion miles per day. So why can’t ordinary people, and ordinary cars, collect map data?

Bee Maps is built with data from the Hivemapper Network

The Hivemapper Network, launched in 2022, is an open, global, decentralized mapping network that relies on a mix of humans and AI to build a map from the driving we do everyday. Thanks to its vibrant contributor community, Hivemapper collects millions of kilometers of road-level imagery every week.

Bee Maps, the owner of this page, is a licensed developer in the Hivemapper ecosystem. Bee Maps provides products and services that make it easy for end users such as enterprises, app developers and government agencies to tap into the rich data on the Hivemapper Network.

The Problems We’re Solving

1. Uneven coverage and freshness - Typical methods of collecting map data are very expensive, so even the best-funded companies struggle to refresh maps at global scale.

2. Fresher maps for autonomous and ADAS driving - Today's maps were made for humans. The maps required by autonomous and semi-autonomous vehicles require far fresher data.

3. Expensive for businesses - Millions of businesses pay to integrate maps into their products. With so few choices for reliable maps, monopoly pricing makes map data unaffordable.

4. Today's maps don't understand the "why" - When cars start to travel at 10 mph on a road they normally travel at 40 mph, modern maps don't know if this is due to road construction, a minor fender-bender or a severe crash that will take hours to clear. Even when a user reports an issue through an app, they cannot immediately trust the report without imagery.

The documentation in this repository is intended to help people learn about Bee Maps products and learn how to use them. If you can’t find the answers you need, just fill out this form on our homepage, and our sales team will get in touch with you.

Thank you for being a part of the future of maps.

-The Bee Maps team

Basics of mapping with Bee

Is my Bee LTE mapping?

There are multiple ways to determine if your Bee is mapping.

1. Confirm via Bee

If you have two blue LEDs on the Bee LTE your devices is mapping.

2. Confirm via Bee Map App

• Connect Bee Maps app to your Bee

• If your icon is blue and pulsing, your Bee is mapping

Tap the Bee image preview to see a larger version and the upload progress (LTE).

Map AI is a fully automated system that processes crowdsourced street-level imagery from the Hivemapper Network into a structured global street level dynamic map - everything from lanes to road rules to dynamic events like road construction, and police activity.

It uses a combination of computer vision and spatial AI pipeline to detect, classify, and geolocate assets like traffic signs, road markings, lane configurations, gas prices, and more. This system is designed to run on edge devices like the Bee enabling cost effective, scalable, high-frequency map updates without the need for traditional manual mapping.

The Map AI pipeline integrates multiple deep learning models that perform image segmentation, object detection, and geospatial positioning alignment. These models are trained to identify street level elements in varied environmental conditions and from different vehicle-mounted camera perspectives. Once detected, each feature (speed limits, toll prices, etc.) is associated with a precise geographic allowing for accurate placement on the map and relationship to other objects.

To continuously improve performance, Map AI outputs are routed through an optional human-in-the-loop system involving AI Trainers. These contributors validate and correct model predictions through structured review tasks, feeding that data back into the training pipeline. This hybrid approach ensures high-quality feature extraction even in edge cases or geographies with sparse data, and it supports rapid model iteration as new types of features are added to the detection set.

Bee Maps is built with data from the Hivemapper Network, whose mission is to build a useful map for people everywhere to use while protecting their privacy. The personal information and location data of Hivemapper Network contributors and Bee Maps customers is not the product. For this reason, the network has been designed to be private and anonymous, and to uphold the highest standards of data protection and privacy for both contributors and bystanders.

You can find more information on the privacy center, a comprehensive portal that includes all the relevant information about privacy at Hivemapper, including:

• Key aspects of data collection and data products generated from map imagery

• A list of cities and countries where mapping collection is occurring each quarter

• The current Privacy Policy

Here are some of the ways that we implement "privacy by design."

Anonymous Usernames

Bee Maps will never ask contributors to share personal information such as phone numbers, credit card numbers, or home addresses, except when absolutely necessary to fulfill a shipment. The Hivemapper Network generates random three-word usernames to protect the identity of its contributors, and asks contributors not to share their usernames anywhere to shield their identities.

Anonymized Location Data

The location data in the Hivemapper Network Coverage Map is not associated with a username. Hivemapper doesn’t share usernames or places that have been mapped, so no one will know those locations unless provided. The Hivemapper Network uses various means to verify mapping data location while allowing contributions to remain anonymous.

Trip Trimming

The first 500 meters and the last 500 meters of a given trip are automatically discarded. A contributor can adjust this up to 1,000 meters. This feature cannot be disabled.

Personal Privacy Zones

This feature enables a contributor to define specific geographic areas — be it around their home, workplace, or any other location — as zones where their device will stop recording. Whenever the contributor’s device enters a personal privacy zones, it automatically pauses data collection. This eliminates a contributor’s need to manually stop or disable the device as they navigate spaces that they don’t want to map.

Personal Privacy Zones are never shared with Hivemapper servers, and remain confidential only to the contributor.

Network Privacy Zones

Network Privacy Zones extends privacy to sensitive areas where everyone’s data collection will be paused. If a location such as a military base, nuclear power plant, or private industrial facility is designated as a Network Privacy Zone, the Hivemapper Network automatically blocks collection within that area.

Contributors Know When They Are Mapping

All Hivemapper devices make it clearly visible to the contributor when they are actively mapping via LED lights and via the companion app. Bee Maps built on the Hivemapper Network is transparent about the data that contributors are collecting and how it is leveraged to build the network and Bee Maps. Furthermore, the Hivemapper Dashcam is an open-source device, and anyone can inspect the code that determines what is collected.

Blurred Faces, Bodies, Vehicles, and License Plates

The Hivemapper Network uses computer-vision algorithms to blur out faces, bodies, vehicles, license plates and faces to protect the privacy of anyone who happens to be captured in mapping images. For example, the image below shows a submission from a Hivemapper contributor that went through privacy blurring. Blurring occurs automatically on the edge on all device models.

Submitting a Redaction Request

Bee Maps and the Hivemapper Network can assist with blurring or deletion of personal information that is inadvertently collected by the network. If you have a request, please fill out the request form in our privacy center or contact us at privacy@hivemapper.com. To help Hivemapper identify the relevant materials, please include the following pieces of information in your message:

• The three-word username of the contributor and the time window when the collection occurred.

• The street address where the collection occurred and a description of the precise area, including landmarks such as position relative to adjacent streets.

• The type of private information that was collected.

Placards for Mappers

In certain countries, we work to ensure that bystanders are aware that a device is collecting for a map, device contributors mount a placard provided by Hivemapper.

Blockchain and Wallets

Blockchain technology facilitates a new level of encryption, privacy, and anonymity. The Hivemapper Network is built on the Solana blockchain.

Hivemapper Network contributors and Bee Maps customers who receive HONEY require a crypto wallet to be connected to the Hivemapper and Bee Keeper app. Generally, wallets don’t track personally identifiable information and are not necessarily linked to your identity.

Government Privacy Regulators

The Hivemapper Network proactively works with government regulators to ensure that our privacy standards meet local regulations and are the best in the industry.

Overview

Bee Maps designed the Map Image API to allow developers and enterprises to easily access imagery from the Hivemapper Network.

Map Image API Developer Docs and Tools

• Developer documentation for Map Data APIs can be accessed here.

• You will need an API Key, see here for instructions.

• Hive-Py is a Python wrapper for the Map Image API, see GitHub here.

Example query Python query using Hive-Py

> python -m imagery.query
usage: query.py [-h] -i INPUT_FILE [-s START_DAY] [-e END_DAY] [-L] [-x] [-d MAX_DIST] [-l MAX_LAG] [-z MAX_ANGLE] -o OUTPUT_DIR [-g] [-w WIDTH] [-M]
                [-I CUSTOM_ID_FIELD] [-S CUSTOM_MIN_DATE_FIELD] [-k] [-E] [-K SKIP_GEO_FILE] [-P IMAGE_POST_PROCESSING] -a AUTHORIZATION [-c NUM_THREADS] [-v]
                [-C] [-b] [-N]

Sample Map Image API data

Before using the API, you can quickly evaluate sample imagery that was collected via front-facing and side-facing devices.

Imagery specs

• Forward facing (interior or exterior mounted)

• 1080p

• Lane-level positional accuracy

• Frames collected and uploaded every 6 to 8 meters — can be dynamically adjusted in certain regions.

Purchase Map Credits

You can purchase Map Credits via self-serve Console > Developers to use the Map Image API.

If you're a customer interested in accessing the world's freshest map data products, Console is the place to go. This one-stop shop offers all the core features needed to access Bee Maps products.

Create Account

Get started by logging into Console using a Google account. You can also create/link a Phantom or Breeze account, but Google is the preferred login method for Console.

Buy Map Credits

Map Credits are needed to access Bee Maps data products, including the Map Image API, Map Features API and Scout. Map Credits can only be purchased after logging in. Once logged in, you can purchase Map Credits through Console > Organization.

Each Map Credit costs $0.02. This means that $1 buys 50 Map Credits, which is roughly equivalent to one kilometer worth of imagery from a single week, or 1 kilometer of a single class of Map Features for a week. There is a minimum purchase of $10, equivalent to 500 Map Credits, with each transaction.

Generate API Key

To use Bee Maps APIs, an API key must be generated and active. To generate an API key:

1. Navigate to Console > Developers > API Key

2. Click Generate API Key

3. Active API keys will will be listed under Active API Keys

For Developers

• In your API call, add the base64 encoded username:APIKey

  Copy

  Basic dXNlcm5hbWU6MDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDAwMDA=

After generating an API key and purchasing Map Credits, you now have access to the Map Image API, Map Features API, and Scout.

Overview

Bee Maps designed the Map Features API to allow developers and enterprises to easily access Map Features detected using imagery from the Hivemapper Network.

Bee Maps devices are designed to automatically detect objects such as speed limit signs, traffic light signals, turn restriction signs, etc. When detected objects are properly and successfully geo-located, they become map features that are accessible via the Map Features API.

Supported Map Features

The list of supported Map Features will constantly expand. Below are the currently supported Map Features by country and region.

API Endpoint Docs and Tools

• Developer documentation for Map Data APIs can be accessed here.

• You will need an API Key, see here for instruction

• Hive-Py is a Python based wrapper that allows you to query map features.

Example Python query for Map Features using Hive-Py

> python -m mapfeatures.query
usage: query.py [-h] -i INPUT_FILE -o OUTPUT_DIR [-w WIDTH] -a AUTHORIZATION [-c NUM_THREADS] [-v]

options:
  -h, --help            show this help message and exit
  -i INPUT_FILE, --input_file INPUT_FILE
                        Input file
  -o OUTPUT_DIR, --output_dir OUTPUT_DIR
  -w WIDTH, --width WIDTH
  -a AUTHORIZATION, --authorization AUTHORIZATION
  -c NUM_THREADS, --num_threads NUM_THREADS
  -v, --verbose
  -z, --zip_images

Map Feature Data Schema

Below is an example of the data schema for a map feature.

{
  "id": "SLS299345",,
  "objectClass": "speed-limit",
  "properties": {
    "speedLimit": 35,
    "unit": "mph",
    "regulatory": "enforced",
  },
  "position": {
      "lon": -108.123,
      "lat": 34.234,
      "azimuth": 90,
      "height": 0.5,
      "width": 0.3
  },
  "observed": {
      "confidence": 0.9,
      "frameId": 1922121212933
      "firstSeen": "2023-05-05T00:00:00.000Z",
      "lastSeen": "2023-05-05T00:00:00.000Z",
  },
}

Description:

• id – Unique ID for each map feature.

• objectClass – The name of the object class, e.g., speed limit or stop sign.

• properties – These provide the context and details for the map feature.

• lat/lon – The coordinates for the object.

• height – The height of the object.

• width – The width of the object.

• azimuth – The direction in which the object is facing, e.g., the sign is facing northbound traffic.

• confidence – The confidence that this object has been successfully identified and geo-located to create or update a map feature.

• frameId – The associated image frame(s) that were used to generate this map feature.

• firstSeen – The first time Hivemapper has seen and detected this object.

• lastSeen – The last time Hivemapper has seen and detected this object.

Map Feature History

For a given map feature ID, you can request its history to review changes. Below is an example of a history for a given map feature.

/**
 * GET features/:feature
 * position always in NE reference
 */
{
  "id": "SLP001",
  "status": "void",
  "class": "speed-limit",
  "position": {
    "lon": -108.123,
    "lat": 34.234,
    "azimuth": 90,
    "height": 0.5,
    "width": 0.3
  },
  "history": [
    {
      "date": "2023-02-05T22:43:28.067Z",
      "changeType": "created"
    },
    {
      "date": "2023-03-06T22:43:28.067Z",
      "changeType": "updated",
      "speedLimit": 30
    },
    {
      "date": "2023-04-07T22:43:28.067Z",
      "changeType": "updated",
      "position": {
        "lon": -108.124,
        "lat": 34.235,
        "azimuth": 89,
        "height": 0.5,
        "width": 0.3      
      }
    },
    {
      "date": "2023-05-07T22:43:28.067Z",
      "changeType": "inactive",
    },
    {
      "date": "2023-06-07T22:43:28.067Z",
      "changeType": "active",
    },
    {
      "date": "2023-07-07T22:43:28.067Z",
      "changeType": "void",
    }
  ]
}

Highway Exit Signs

Only exit signs that include the exit location — not upcoming exits.

{
  "id": "SLS299345",
  "objectClass": "highway-exit-sign",
  "attributes": {
    "regulatory": "guidance",
    "exitNumber": "111A",
    "exitLabel": "Deltona"
  },
  "position": {
    "lon": -108.123,
    "lat": 34.234,
    "azimuth": 90,
    "height": 0.5,
    "width": 0.3
  },
  "observed": {
    "confidence": 0.9,
    "firstSeen": "2023-05-05T00:00:00.000Z",
    "lastSeen": "2023-05-05T00:00:00.000Z",
    "frameId": 1922121212933
  }
}

Do Not Enter Sign

{
  "_id": "66c7908e51ac6a21aaa390f0",
  "label": "do-not-enter-sign",
  "mapFeatureClass": "do-not-enter-sign",
  "pos": {
    "type": "Point",
    "coordinates": [-97.73590476857619, 30.267051606956315]
  },
  "azimuth": 17.435000000000002,
  "width": 0.4884808858235677,
  "height": 0.5045814514160156,
  "firstObservedAt": "2024-07-31T00:18:58.480Z",
  "lastObservedAt": "2024-08-15T23:32:25.361Z",
  "confidence": 0.9729349754632881,
  "createdAt": "2024-08-22T19:25:02.615Z",
  "updatedAt": "2024-08-26T08:37:24.252Z"
}

Fire Hydrants

{
  "_id": "6807e1cb4d175ef0ba353dc0",
  "label": "fire hydrant",
  "pos": {
    "type": "Point",
    "coordinates": [-118.71440357611763, 34.27917116391626]
  },
  "azimuth": 79.63100535550997,
  "width": 0.7500454545454546,
  "height": 0.75,
  "firstObservedAt": "2025-04-11T13:45:58.693Z",
  "lastObservedAt": "2025-04-17T15:03:12.700Z",
  "confidence": 0.5,
  "createdAt": "2025-04-22T18:36:59.132Z",
  "updatedAt": "2025-04-22T18:43:08.170Z"
}

Traffic Lights - Vehicle Intersections

The following attributes are captured for traffic lights at intersections

• Position

• Azimuth

• width

• height

• Vertical or horizontal orientation (coming)

• Number of light bulbs (coming)

{
  "id": "SLS12345",
  "objectClass": "traffic-light",
  "attributes": {
    "applicableVehicles": "all",
    "type": "traffic-intersection"
  },
  "position": {
    "lon": -108.123,
    "lat": 34.234,
    "azimuth": 90,
    "height": 0.5,
    "width": 0.3
  },
  "observed": {
    "confidence": 0.9,
    "firstSeen": "2023-05-05T00:00:00.000Z",
    "lastSeen": "2023-05-05T00:00:00.000Z",
    "frameId": 1922121212933
  }
}

Road Width

Our road width detections encompasses only drivable, paved road surfaces.

No Parking Any Time

{
  "_id": "6807d135e92f768db5b15e02",
  "label": "parking-restriction",
  "pos": {
    "type": "Point",
    "coordinates": [-118.76809392015912, 34.27162502172553]
  },
  "azimuth": 266.0494947076169,
  "width": 0.38048333333333334,
  "height": 0.46,
  "firstObservedAt": "2025-04-15T14:45:18.800Z",
  "lastObservedAt": "2025-04-17T15:24:15.929Z",
  "confidence": 0.5,
  "createdAt": "2025-04-22T17:26:13.700Z",
  "updatedAt": "2025-04-22T17:28:23.770Z"
}

No Parking (symbol) (Times)

{
  "_id": "6807d0ffe92f768db5b14c9d",
  "label": "no-parking-symbol",
  "pos": {
    "type": "Point",
    "coordinates": [-118.32941260612121, 34.09646917678104]
  },
  "azimuth": 177.1451,
  "width": 0.5812,
  "height": 0.61,
  "firstObservedAt": "2025-04-20T15:38:54.522Z",
  "lastObservedAt": "2025-04-20T15:38:54.522Z",
  "confidence": 0.5,
  "createdAt": "2025-04-22T17:25:19.974Z",
  "updatedAt": "2025-04-22T17:28:28.367Z"
}

No Parking (Times)

{
  "_id": "6807d0d0e92f768db5b147bd",
  "label": "parking-restriction",
  "pos": {
    "type": "Point",
    "coordinates": [-118.34119798990473, 34.14406901700743]
  },
  "azimuth": 17.788340934955887,
  "width": 0.5188333333333334,
  "height": 0.4686333333333333,
  "firstObservedAt": "2025-04-11T00:29:32.575Z",
  "lastObservedAt": "2025-04-19T17:08:45.948Z",
  "confidence": 0.5,
  "createdAt": "2025-04-22T17:24:32.494Z",
  "updatedAt": "2025-04-22T17:28:23.078Z"
}

No Parking Except (Days)

{
  "_id": "6807d0c8e92f768db5b13b84",
  "label": "parking-restriction",
  "pos": {
    "type": "Point",
    "coordinates": [-118.60594666010942, 34.25823425041381]
  },
  "azimuth": 181.66481110398234,
  "width": 0.431925,
  "height": 0.46,
  "firstObservedAt": "2025-04-14T22:26:14.574Z",
  "lastObservedAt": "2025-04-15T16:40:32.958Z",
  "confidence": 0.5,
  "createdAt": "2025-04-22T17:24:24.613Z",
  "updatedAt": "2025-04-22T17:28:23.539Z"
}

(Time) Parking (Times)

No Parking Loading Zone

No Parking Bus Stop

Reserved Parking (Accessible)

No Parking Bike Lane

(Time) Pay Parking

Pay Parking (Time Limit)

Pay Parking

Pay Parking (Times)

Parking (Limit & Time)

No Parking Bus Stop

No Parking Transit Logo

(Time Limit) Parking (Times)

{
  "_id": "6807cf05f426a4d6374563d0",
  "label": "parking-information",
  "pos": {
    "type": "Point",
    "coordinates": [-118.44728242454215, 34.167893750711286]
  },
  "azimuth": 230.81594999999996,
  "width": 0.33895,
  "height": 0.46,
  "firstObservedAt": "2025-04-17T19:27:33.323Z",
  "lastObservedAt": "2025-04-17T19:27:33.323Z",
  "confidence": 0.5,
  "createdAt": "2025-04-22T17:16:53.313Z",
  "updatedAt": "2025-04-22T17:28:22.783Z"
}

No Parking / Restricted Parking Combo (Side by Side)

No Parking / Restricted Parking Combo (Stacked)

{
  "_id": "6807cfe45425126a470d9d6a",
  "label": "parking-restriction",
  "pos": {
    "type": "Point",
    "coordinates": [-118.36395305509234, 33.89975524577228]
  },
  "azimuth": 89.7938,
  "width": 0.5801499999999999,
  "height": 0.46,
  "firstObservedAt": "2025-04-15T18:36:30.557Z",
  "lastObservedAt": "2025-04-20T16:30:42.191Z",
  "confidence": 0.5,
  "createdAt": "2025-04-22T17:20:36.690Z",
  "updatedAt": "2025-04-22T17:28:23.695Z"
}

Vertical Height Restriction

{
  "_id": "6807c9e5e6d0cdf5849f0dd0",
  "label": "height-restriction-sign",
  "pos": {
    "type": "Point",
    "coordinates": [-118.28052415189077, 33.97080464414825]
  },
  "azimuth": 89.16191226226074,
  "width": 0.43070220947265625,
  "height": 0.6550998687744141,
  "firstObservedAt": "2025-03-25T14:35:18.501Z",
  "lastObservedAt": "2025-03-25T14:35:18.501Z",
  "confidence": 0.5,
  "createdAt": "2025-04-22T16:55:01.944Z",
  "updatedAt": "2025-04-22T16:58:16.809Z"
}

Speed & Red Light Cameras

{
  "_id": "6807dba1f76b0f61a7f61b3d",
  "label": "camera",
  "pos": {
    "type": "Point",
    "coordinates": [-111.6805406605749, 33.32264912402475]
  },
  "azimuth": 226.2096505270454,
  "width": 0,
  "height": 0,
  "firstObservedAt": "2025-03-25T14:18:33.903Z",
  "lastObservedAt": "2025-03-25T14:18:33.903Z",
  "confidence": 0.5,
  "createdAt": "2025-04-22T18:10:41.846Z",
  "updatedAt": "2025-04-22T18:13:10.313Z"
}

Stop Signs

Only at intersections, not warning signs of stop ahead.

{
  "id": "SLS123323",
  "objectClass": "stop-sign",
  "attributes": {
    "regulatory": "enforced"
  },
  "position": {
    "lon": -108.123,
    "lat": 34.234,
    "azimuth": 90,
    "height": 0.5,
    "width": 0.3
  },
  "observed": {
    "confidence": 0.9,
    "firstSeen": "2023-05-05T00:00:00.000Z",
    "lastSeen": "2023-05-05T00:00:00.000Z",
    "frameId": 1922121212933
  }
}

Toll Prices

{
  "_id": "680793fe64540cd6b00cd17a",
  "label": "toll-price-sign",
  "pos": {
    "type": "Point",
    "coordinates": [-118.09008373783647, 33.77886380466568]
  },
  "azimuth": 350.3929541415611,
  "width": 1.1873550415039062,
  "height": 0.2642993927001953,
  "firstObservedAt": "2025-03-25T19:52:08.539Z",
  "lastObservedAt": "2025-03-25T19:52:08.539Z",
  "confidence": 0.5,
  "createdAt": "2025-04-22T13:05:02.002Z",
  "updatedAt": "2025-04-22T13:13:12.928Z"
}

Overview

Beekeeper is an AI that sees everything your drivers see—in real-time. It doesn’t just monitor drivers and vehicles for safety, it continuously maps the outside world, turning every trip into actionable intelligence for your entire fleet.

Who it's for?

Beekeeper AI is designed for teams with commercial vehicles — delivery, logistics, medical, waste management, utilities, timber, medical services, and local services.

See pricing for Beekeeper AI here.

The Beekeeper Solution

There are two parts of the solution:

1. Bee LTE

The Bee is a professional grade AI powered camera for your vehicles used by tens of thousands of drivers all over the world. It requires an active cellular data plan.

2. Beekeeper AI Software

Beekeeper AI doesn’t just collect data—it sees and understands the world in real-time. Your fleet gets intelligence directly from the road, helping drivers make smarter decisions on fuel, routes, deliveries, and more.

• AI Intelligence

  • Ask questions and get answers

  • Get clear analytics and automated insights with intuitive charts and graphs.

• Live Monitoring

  • Get live tracking, historic drive paths, and last-known locations, giving you total control and clarity over your fleet's movements.

• Trip History

  • Provides a comprehensive record of all vehicle journeys.

• AI-Powered Event Detection:

  • Leveraging cutting-edge AI, our system detects events like swerving, harsh braking, rapid acceleration, and speeding in real time. This ensures that potential risks are flagged immediately, allowing you to address issues before they escalate.

The best way to learn what Beekeeper can do is to start using it. In the meantime, here’s a quick overview of core product capabilities:

AI Reports

What is Beekeeper Intelligence?

AI tools that give you automated reports (AI Reports) and the ability to ask questions (AI Assitant) about your fleet and the thing they are seeing.

AI Reports

Reports we create automatically that are related to key questions about your fleet

AI Assistant

• What % of my drivers had safety related AI Events in the last 7 days?

• Have any of my drivers been near 1600 Pennsylvania Ave in the past 24 hrs?

• What cities are my drivers doing the most stops in?

Live Monitoring

What is Live Monitoring?

• Status of every vehicle from - driving, idle, offline and more

• Last location

• See what they see - fetch an image from the Bee to see what the driver is seeing

• Lock your devices to your fleet to safeguard your Bee assets

• Stats on your drivers

Driver Profile

What is Driver Profile?

• Driver mileage metrics

• LTE usage metrics

• LTE carrier information e.g. IMEI

• Bee LTE firmware - checkmark means the Bee is on the latest firmware.

Trip History

What is Trip History?

Trip History provides a comprehensive record of all vehicle journeys, including:

• Start and end times for each trip

• Stops made with duration

• Total distance and trip duration

• Location of each stop

• Total trips for the day or week, and total mileage.

AI Event Detections

What are AI Event detections?

When a driver triggers an AI safety event a 10 to 30 second video is uploaded. Currently supported events include:

Search

Search your Beekeeper for:

• Locations and addresses

• Driver Name

• Device ID

• License Plate

• Driver Status

• Vehicle Type

Settings

Easy to setup your account and add your team members to Beekeeper.

Roadwork Construction

Our roadwork construction detections encompass the following data attributes:

• Where the construction impact starts on a road

• Where the construction ends on a road

• Number of lanes impacted.

We also have an awareness if construction ended if the road was mapped and construction was not detected.

Setup your fleet

Add devices to your fleet

To add devices to your existing fleet, simply repeat step 1 and 2 above using the same email address you used in Step 2.

For example, in step 2, we used bob@email.com to create the Bob Logistics fleet. So, we would use that same email address for future devices to auto-add them to our fleet.

API Key Provisioning

• Go to the Integrations tab

• Click Generate API Key

• Copy and save the key securely — it will only be shown once

Authorization

All API requests require the API Key in the header:

Devices API

Endpoint

GET https://api.trybeekeeper.ai/v1/devices

Returns a list of all devices in your fleet.

Response Format

Location API

Endpoint

GET https://api.trybeekeeper.ai/v1/location

Query Params

• deviceId (required)

Returns the latest known location of the specified device.

Response Format

Trips API

Endpoint

GET https://api.trybeekeeper.ai/v1/trips

Query Params

• deviceId (required)

• startDate (required, ISO format)

• endDate (required, ISO format)

Returns trips taken by a device within a specified date range.

Response Format (truncated for clarity)

Rewards API

Lists rewards information for all devices in fleet, for a given reward period. A reward period is a calendar week.

Endpoint

GET https://api.trybeekeeper.ai/v1/hivemapperRewards

Query Params

• rewardPeriod required. date must be a Monday e.g. 2025-05-12

Returns rewards for your devices in your fleet

Response Format

Does Beekeeper require the Bee LTE model?

• Yes, and it requires an active cellular data plan

How do I know if the firmware of my Bee devices is up to date?

• A checkmark under the driver profile means the Bee is running the latest firmware

• Firmware updates are automatic OTA (over-the-air) and require no manual work

Can I use my own SIM card in the Bee LTE?

• Yes, as long as it’s compatible with the supported networks in your region

• SIM card size for the Bee is nano

Can I disable the USB data port on the Bee for my fleet?

• Yes, this stops all Bees from recording to USB drives, even if plugged in.

• Go to

  • Beekeeper Settings

  • Go Fleet Settings

  • USB Recordings

Can I connect the Bee to the OBD-2 port?

Does the Bee require professional installation?

• No—it takes under 5 minutes to install. Just plug it in, mount it, and you’re good to go

Is there a microphone or speaker on the Bee?

• No

Does the Bee have an internal facing camera to spy on drivers?

• No—most data doesn’t require an internal camera, and it’s a bit creepy.

Can I lock devices to my Beekeeper fleet?

• Yes, just add them to Beekeeper and they will be locked to your fleet.

Is Beekeeper supported in all countries?

• No, its no supported in Iran, North Korea, Russia, China, and a few other smaller countries where we are restricted from selling the Bee LTE devices.

What happens if my vehicle was in an accident?

• If a Beekeeper AI Event detection was not triggered we store the last 10 minutes of video on the device, so be sure to turn the device off and contact customer support.

What happens if the Bee devices lose LTE signal?

• It will appear in the Monitoring list as "Searching" — once it regains LTE it will upload everything it stored on the device when it had no LTE connection.

Can I see the mount rating for my devices?

• Yes, under the Assistance tab there is a report that provides mount ratings for each Bee device.

Are Bee devices in a Beekeeper fleet contributing to Hivemapper

Can I access trip history and events in real-time?

• Yes, Beekeeper shows live trip activity and logs events as they happen.

• Trip history is also stored and searchable.

Can I assign drivers or vehicles to specific Bees?

• Yes, Beekeeper lets you tag and label devices for better organization. See the driver profile

Can I remove a Bee device from my fleet?

• Yes, by connecting the Bee App to the Bee you can remove it from your fleet

Can I see how much LTE data my fleet is using?

• Yes, under the Assistant tab it shows LTE data usage by device and overall

• You can also view LTE usage per device in the Driver Profile

How long are video clips from AI Events retained for?

• 6 months

How frequently can AI Reports be refreshed?

• Every 60 minutes

Webhook Provisioning

• Log in to your Beekeeper Dashboard

• Go to Settings

• Go to the Webhooks tab

• Click Create Webhook

• Copy and save the token securely — it will only be shown once

Authorization

All webhook payloads are signed with a Bearer token:

Authorization: Bearer <your webhook token>

Retry Policy

• Webhooks are not retried

• If a webhook delivery fails (non-200 response or timeout), it is skipped

• The next eligible update will be sent normally

IP Whitelisting

Coming soon – You’ll be able to restrict incoming requests to known IP ranges.

Location Updates Webhook

Trigger Fires whenever a device's location changes.

Payload Format

{
  "device": { "id": "681da6f00000000000000000", "name": "Device A" },
  "lat": 37.7371066,
  "lon": -122.4027606,
  "speedKmH": 89.37,
  "timestamp": "2025-05-09T15:58:59.465Z"
}

Supported mobile carriers

Uploading through LTE is one of the core features of the Bee LTE model. Below are the known supported carriers by region.

Purchase a physical nano SIM card

You will need a physical Nano SIM card from a supported mobile carrier that has data enabled.

Insert nano SIM card into your Bee

Powering up

1. Locate the 12 volt accessory outlet in your vehicle

2. Plug in the included outlet adaptor

3. Locate the power port on the underside of the Bee and plug in the other end of the cord

LED for Power

Approved vehicles mount positions

✅ = 🚘 🚛

Vehicles with at least four wheels are currently approved including cars, vans and trucks of all sizes.

❌ = 🏍️

Vehicles that do not have four wheels are not approved at this time. This includes: bicycles, e-bikes, scooters, motorcycles.

Forward Facing Only

Example Approved Mounts

What’s Included

• Bee device

• Safety Pamphlet

• 12/24V Auxiliary Power Cord

• Car Mount

• Bee Mount Bracket and 3 screws

• 2 Allen Wrenches

• SIM slot cover and 2 screws

• Screwdriver

Bee Mount Assembly

What is the Bee?

Get Started with the Bee

Everything from assembling your Bee to driving and mapping with your Bee. We have a guide for you.

Download Bee Maps App

• Download for iOS in the App Store.

• Download for Android in the Play Store.

Open the Bee Maps app once it's finished installing.

Connect Bee Maps App to Bee (iOS)

• Turn on your iPhone's WiFi

• From the Bee Maps App home screen, tap the Connect button.

• You will be automatically directed to your iPhone's Wi-Fi network settings.

• Select the Bee's Wi-Fi network — dashcam followed by numbers dashcam-0123456789ABCDEF.

• Enter the password hivemapper (all lowercase).

• Navigate back to the Bee Maps app.

• Bee is now connected. You should now see a live preview at the top of the home screen as shown below.

Connect Bee Maps App to Bee (Android)

1. Power on the Bee.

2. Open the Bee Maps app on Android.

3. On the main screen, tap the Connect button.

4. Wait for your Bee’s name to appear in the tray.

5. Select your Bee — e.g. dashcam-0123456789ABCDEF.

6. If prompted, Allow discovery of local WiFi networks.

7. Wait a few moments for the app to connect to the Bee.

8. Bee is now connected. You should now see a live preview at the top of the home screen as shown below.

Is my Bee LTE Activated?

After inserting an active SIM card into your Bee this will help you confirm that your Bee is mapping passively.

The first time you connect to your Bee via the Bee Maps App you should see a notification showing you that your LTE is active.

APN Setting

If your SIM card is active but you don't have service you may need to add APN SIM settings for your mobile carrier.

• Connect Bee Maps App to your Bee

• Go to Settings

• Go to Bee

• Go to Advanced

• Go to APN Settings

• Follow the instructions for adding your APN Settings

Mount check

2. Go to Settings

3. Go to Bee

5. Follow the instructions on the screen to adjust the Clarity and Tilt

Tips for Improving Mount Quality

• Mount the Bee on the front windshield with a clear, unobstructed view of the road. Avoid areas with tint, black coatings, dot patterns, or interior accessories.

• Do not block the driver’s view. Choose a safe, low-impact mounting spot.

• Avoid tinted windows and minimize visibility of your vehicle’s interior in the frame.

• Remove personal items from the dashboard—name tags, documents, or anything that could identify you.

• Make sure the Bee is level—not pointed too far up at the sky or too far down at the hood.

• If using AI event detection, follow the official Bee Placement and Detection Guidelines for best results.

View your mount rating

• Go to Settings

• Go to Profile

To improve your mount rating, you may need to change your mount positioning or location.

Firmware updates for Bee LTE

No action needed. Bee LTE updates firmware automatically via OTA (over-the-air).

Firmware updates for Bee WiFi

Connect your wallet

• Open Bee Maps App

• Go to Settings

• Click on Connect Wallet

Uploads automatically

No action needed. In LTE mode, your contributions upload automatically from the Bee LTE.

Want to Confirm Bee LTE is uploading?

The Bee LTE uploads automatically, but you can watch if you’re curious.

• Connect Bee Maps App to your Bee

• Tap the Viewer in the home screen of the app

• Progress bar on top of expanded viewer appears as shown

How much data is my Bee uploading?

• Connect Bee Maps App to your Bee

• Settings > Data

Step 1 - Connect your wallet

• Open Bee Maps App

• Go to Settings

• Click on Connect Wallet

Step 2 - Connect Bee Maps App to your Bee

The Bee Maps app can be used to upload mapping data captured by the Bee to the Hivemapper Network. When using this method, the Bee Maps app acts as a bridge between your Bee device and the Hivemapper Network.

• Once connected, the app will begin downloading collected data from your Bee (blue progress bar) to your mobile device.

Step 3 - Upload map data from your phone

The turquoise progress bar indicates the upload process. There are two ways to upload from your phone.

• Upload via WiFi

  • By default, the app will wait for a trusted Wi-Fi network (like your home or office) to begin uploading to the Hivemapper Network.

  • Uploads happen automatically in the background.

• Upload via cellular data

  • Enable the option in the Bee Maps app > Settings > App

  • Toggle the “Use iPhone Cellular Data” button to start uploading via your phone’s cellular data plan.

How much data is my Bee uploading?

• Connect Bee Maps App to your Bee

• Settings > Data

Gas Prices

Fleet

How do I add an existing Bee device to a Beekeeper fleet?

• See here.

Can I add a Bee WiFi model to a Beekeeper fleet?

• No. Only a Bee LTE model can be added to a fleet.

Can I lock a Bee device to my Beekeeper fleet?

• Yes, the Bee LTE device will only work for your fleet once added to your fleet.

Device

Will the Bee device map while also performing safety and monitoring functions for Beekeeper?

• Yes. It's a dual purpose device.

My Bee LTE is not connecting, what do I do?

• Make sure you have an active SIM card inserted properly.

• Verify your APN Settings via the app

  • Connect to your Bee from Bee Maps App

  • Settings > Bee > Advanced > APN Settings and follow instructions

Will the Bee continue to operate when it loses connectivity?

• Yes, if your Bee LTE loses connectivity it will continue to perform and once it regains connectivity it will send updates.

My Bee LTE is not connecting, what do I do?

• Make sure you have an active SIM card from a supported mobile carrier inserted properly.

• Verify your APN Settings via the app, see above.

Can I plug my Bee into any USB port in my vehicle?

• Yes, but not all USB ports are supported, it needs to be a USB-PD to provide sufficient power.

How much video is stored on the Bee device?

• Up to 10 hours of video are stored on the device and can be retrieved remotely via Beekeeper.

• You can also insert your own USB stick into the Bee and record as much as you like.

What is the max voltage that Bee accepts?

• The Bee accepts a maximum direct voltage of 20V. If you provide more than 20V, you may cause damage to your Bee. See here for power details.

Mapping and Privacy

Are my contributions anonymous?

• Yes, the Hivemapper Network takes privacy seriously.

How can I protect my privacy?

Whether you are a consumer or business operating a fleet, we take your privacy seriously and provide multiple ways to ensure that your devices are not mapping where you don't want them mapping.

• Automatic Trip Trimming

  • Open Bee Maps App

  • Go to Settings

  • Go to Privacy

• Personal Privacy Zones

  • Open Bee Maps App

  • Go to Settings

  • Go to Privacy

• Network Privacy Zones are places like military bases where no mapping occurs.

  • Set by Hivemapper Network.

Where can I mount my Bee?

See here for approved mount positions.

How can I tell if my Bee is mapping properly?

See here for approved mount positions.

Who owns the mapping data produced by the Bee?

The Hivemapper Network.

Where and when can I map?

• Any road.

• 24x7.

Turn Restrictions

Support for the following types of no turn restriction signs:

• No left-turn

• No right-turn

• No right-turn on red

• No left-turn and no u-turn

• No u-turn

• No turn with time restrictions

No Left Turn

{
  "id": "SLS233945",
  "objectClass": "turn-left-restriction",
  "attributes": {
    "regulatory": "enforced",
    "turn-left-restriction": "true"
  },
  "position": {
    "lon": -108.123,
    "lat": 34.234,
    "azimuth": 90,
    "height": 0.5,
    "width": 0.3
  },
  "observed": {
    "confidence": 0.9,
    "firstSeen": "2023-05-05T00:00:00.000Z",
    "lastSeen": "2023-05-05T00:00:00.000Z",
    "frameId": 1922121212933
  }
}

No Right Turn

{
  "id": "SLS093345",
  "objectClass": "turn-right-restriction",
  "attributes": {
    "regulatory": "enforced",
    "turn-right-restriction": "true"
  },
  "position": {
    "lon": -108.123,
    "lat": 34.234,
    "azimuth": 90,
    "height": 0.5,
    "width": 0.3
  },
  "observed": {
    "confidence": 0.9,
    "firstSeen": "2023-05-05T00:00:00.000Z",
    "lastSeen": "2023-05-05T00:00:00.000Z",
    "frameId": 1922121212933
  }
}

No U-Turn

{
  "id": "SLS19945",
  "objectClass": "turn-u-restriction",
  "attributes": {
    "regulatory": "enforced",
    "turn-u-restriction": "true"
  },
  "position": {
    "lon": -108.123,
    "lat": 34.234,
    "azimuth": 90,
    "height": 0.5,
    "width": 0.3
  },
  "observed": {
    "confidence": 0.9,
    "firstSeen": "2023-05-05T00:00:00.000Z",
    "lastSeen": "2023-05-05T00:00:00.000Z",
    "frameId": 1922121212933
  }
}

No U-Turn and No Left Turn

{
  "id": "SL2330295",
  "objectClass": "turn-left-u-restriction",
  "attributes": {
    "regulatory": "enforced",
    "turn-u-restriction": "true",
    "turn-left-restriction": "true"
  },
  "position": {
    "lon": -108.123,
    "lat": 34.234,
    "azimuth": 90,
    "height": 0.5,
    "width": 0.3
  },
  "observed": {
    "confidence": 0.9,
    "firstSeen": "2023-05-05T00:00:00.000Z",
    "lastSeen": "2023-05-05T00:00:00.000Z",
    "frameId": 1922121212933
  }
}

What is Beekeeper?

• Beekeeper is a web based software product for managing a fleet of devices.

• It's primarily for commercial fleets with 5 or more Bee LTE devices.

• Beekeeper has free and paid tiers.

Get started with Beekeeper?

• Learn about Beekeeper capabilities. See here.

• Setup and add Bee LTE devices to a fleet. See here.

Building

At its core, the Bee was designed with a modular, plug-in architecture, making it fast and easy to deploy workloads. Starting today, we’re unlocking three powerful capabilities for developers.

1. Run Custom Edge Detections

You can now deploy custom edge detections on the Bee device—models that run alongside (but do not replace) the native Bee Map AI stack. This lets you extend the Bee’s detection capabilities for your own needs, such as identifying specific utility markers, custom signage, or industry-specific infrastructure.

The core object detection model used for map building is maintained and updated by Bee Maps. However, your edge detections can operate in parallel on the device—filtering, tagging, or flagging new visual classes relevant to your operations.

Deploy models via OTA (over-the-air) using Bee Maps’ geo-targeted infrastructure. You can push to specific devices by region—country, state, or metro—allowing you to target detections based on where and what you need to capture.

The Bee runs a high-efficiency, edge-optimized YOLO model in real time on every frame from its 12.3MP camera. With 5.1 TOPS of compute on board, it delivers low-latency inference even in fully offline or low-bandwidth environments.

How to Deploy a Custom Model

• We collaborate with partners to train objects.

• Your model is deployed to a small subset of Bee devices to validate accuracy and recall.

• Once approved, it’s rolled out to your designated geographies via an OTA update to Bee devices.

2. Change Detection

The Bee’s Map AI continuously detects and maps critical road features, including speed limit signs, stop signs, road width, and other street-level attributes. Additionally, when deploying custom object detections—such as utility infrastructure—you can leverage Change Detection to efficiently identify and upload only the changes (deltas), significantly optimizing data transmission.

You can track changes to specific infrastructure objects—like speed limit signs—by uploading a reference dataset in GeoJSON format. Each object should conform to our feature spec, for example:

{
  "id": "SLS1553923",
  "objectClass": "speed-limit",
  "image-detection": "https://your-bucket-name.s3.beemaps.com/path/to/image.jpg",
  "attributes": {
        "speedLimit": 50,
        "unit": "mph",
        "regulatory": "enforced"
      },
   "position": {
      "lon": -108.123,
      "lat": 34.234,
      "azimuth": 90,
      "height": 0.5,
      "width": 0.3
  },
}

Bee Maps automatically partitions and distributes these objects to devices most likely to encounter them. As Bees detect and upload fresh observations, your GeoJSON file is updated. You can subscribe to real-time changes via API to track updates as they occur.

3. Direct Data Offload to Your Cloud

All data generated from your custom edge detections and change detection workflows—along with optional supporting imagery—is automatically streamed via Bee Connectivity Services from the Bee to your Bee Maps developer account. Bee Connectivity Services leverages the device’s built-in LTE and WiFi offload channels, requiring no additional integration work on your part.

Simply configure your endpoint, and the Bee will immediately begin transmitting structured visual data in real time, ready for ingestion into your systems or workflows.

Contact us (hi@hivemapper.com) to become a Bee developer.

Standard Interior Mounts (For most vehicles in typical/normal conditions)

These mounts are ideal for regular passenger cars and light-duty trucks. Perfect for smooth roads and day-to-day usage.

Recommended for: Cars, light trucks, standard use.

Heavy Duty Mounts (Made for exterior use, but suitable for interior mounting)

Ideal mounts for heavy-duty and commercial vehicles, especially those operating on rougher roads or at higher speeds.

Recommended for: Larger trucks, construction vehicles, commercial fleet vehicles, longer use.

Additional Mount Accessories

OBD-2

If you're looking to expand your Bee device’s capabilities, connecting it through your vehicle’s OBD-2 port can provide a direct and reliable power.

Speed Limits

In additional to regulatory speed limit signs (in US the white signs with black lettering); Bee Maps supports a wide range of speed limit signs, including:

• Speed limit for school zones

• Speed limit zone start and zone end (EU)

• Minimum speed limit zone start and zone end (EU)

• Speed limit for construction zones

• Speed limit for trucks

• Speed limit with time restrictions

• Speed limit with minimum speed

School Speed Limit

EU Speed Limit Start

EU Speed Limit End

EU Minimum Speed Limit Start

EU Minimum Speed Limit End

Trucks Speed Limit

Time Restriction Speed Limit