By Justin Carlson. Sources checked November 7, 2026. Documentation review only; not tested hands-on.
Atmocube is a multi-sensor indoor monitor that can feed a building system directly over Modbus or a broker you run, and can also report to Atmotech’s cloud dashboard. It suits buyers who want local building-system access with an optional, published-price cloud API. The central tradeoff: the REST API requires the PRO plan, and sensors differ by SKU, so the model you order decides what you can retrieve.
Best fit and when it may not suit you
Good fit
Buildings that want readings in a BMS over Modbus TCP/RTU, or in BACnet via a third-party gateway, without depending on a cloud account.
Teams running their own MQTT broker or cloud IoT pipeline.
Small pilots that want a published per-device cloud API price (PRO plan) instead of a sales quote.
May be unsuitable
Buyers who need native BACnet on the device: the vendor guide uses a Modbus-to-BACnet gateway.
Projects that need the cloud REST API on the free Basic plan: it is not included.
Anyone who reads the “data ownership” marketing as a licence to resell data: the terms of use prohibit selling data obtained via the products or services.
What this profile covers
Hardware
Atmocube indoor monitor, current SKUs BF2-E, BF2 and BFCO2-E (five earlier SKUs are no longer manufactured)
Platform
On-device access (Modbus RTU/TCP, MQTT, USB CSV) plus the Atmocube cloud dashboard (atmocube.app) and its REST API
Plan
Dashboard Basic (free, no API) or PRO (USD 49 per device per year, includes API); PRO+ by quote
Scope
Commercial and small projects. Positioned for offices and buildings with BMS integration, but sold through a public web store with a published cloud plan price.
Capabilities apply to this setup only. Other Atmotech (Atmotube) products may differ.
Atmocube measurements and units
Parameters reported by Atmocube
Parameter
Type
Unit
Models
Notes
CO2
Measured
ppm
All current SKUs
Sensor principle is not stated on the pages reviewed. [3, 1]
Available Atmocube; choose the SKU that carries the sensors you need. [3]
Gateway or hub
Conditional Not needed for Modbus, MQTT or the cloud. BACnet requires a Modbus-to-BACnet gateway; the vendor recommends an Intesis unit. [10, 9]
Network
Conditional Wi-Fi (2.4 GHz), Bluetooth and RS-485 on all current SKUs; Ethernet and PoE on BF2-E and BFCO2-E only. [3]
Account
Conditional Not needed for on-device access. A dashboard account is needed for the cloud dashboard and API. [1, 5]
Subscription
Conditional None for core measurements and on-device access. The REST API needs the PRO or PRO+ dashboard plan. [1, 4, 5]
Local access, cloud API and export
Atmocube can be read without the cloud. Modbus TCP or RTU lets a BMS poll registers directly, an MQTT client can publish to a broker you run, and the device can write CSV files to a USB drive. BACnet needs an extra gateway that translates Modbus. Modbus is off by default and must be enabled in the configuration tool.
The cloud dashboard adds history, alerts and CSV export. The REST API sits behind the PRO plan, which is priced per device per year, and authenticates with an API key from your dashboard profile. We could not read the full API reference, so endpoint details remain to be confirmed.
Local access
Not publicly documented No local REST API is documented. Other local paths (also listed under other protocols): Modbus TCP (Ethernet or Wi-Fi), Modbus RTU (RS-485), publishing to an MQTT broker you run, and CSV files written to a USB drive. Condition: Modbus is disabled by default and is enabled through the configuration tool or dashboard. [9, 11, 8]
Cloud API
Conditional REST API at api.atmocube.app using an API key from the dashboard profile. Condition: PRO or PRO+ plan only. [5, 4]
Manual export
Available CSV export from the dashboard (multi-device exports arrive as an archive by email) and local CSV logging to a USB drive. Condition: The plan table lists historical data export on the free Basic plan, which keeps 30 days of cloud data. [7, 8, 4]
Other protocols
Available Modbus RTU/TCP, MQTT 3.1.1 (own broker or AWS IoT Core), BACnet via third-party gateway. [3, 9, 11, 10]
Atmocube API details
Authentication
Available Cloud: “Authorization: APIKey …” header with a key from the dashboard. Local MQTT supports TCP or TLS. No authentication is described for Modbus. [5, 11]
Who can access which data
Conditional API keys belong to a dashboard account and cover its registered devices; finer-grained permissions are not documented. [5]
Latest versus historical data
Unknown The REST documentation did not render, so latest versus history endpoints could not be confirmed. Dashboard history and CSV export exist. [6, 7]
Retention
Conditional Cloud storage: 30 days on Basic, “Unlimited” on PRO and PRO+. The device buffers about one week at 1-minute intervals. [4, 1]
Sampling and aggregation
Available Readings are taken about once per second, averaged per minute and sent every minute. [8]
Timestamps and timezone
Not publicly documented Timestamp format and timezone are not described in the pages reviewed. [7, 5]
Rate limits
Not publicly documented No numeric limit. The terms say use may be limited by monthly data transaction volumes and database calls. Modbus minimum poll interval is 1 second (2+ seconds recommended). [14, 9]
Export formats and limits
Available CSV (dashboard and USB); MQTT messages; Modbus registers; JSON REST (format not verified). [7, 8, 11]
Multiple devices and sites
Conditional Basic allows up to 5 registered devices; PRO is unlimited. Multi-device CSV export is supported. [4, 7]
Integrations
Available BMS/BAS via Modbus or BACnet gateway; AWS IoT Core via MQTT; own MQTT server. [4, 11, 10]
Usage and reuse restrictions
Restricted by terms Despite “full data ownership” marketing, the terms of use say you may not sell data obtained via the products or services, limit permitted uses, and claim the compilation of data as Atmotech’s property. The terms of sale say data is for personal use. [14, 15, 1]
Atmocube pricing: hardware, platform and API
Prices are shown only where the vendor publishes them, as checked on November 7, 2026. Taxes, shipping and implementation work are not included.
Atmocube cost components
Component
Item
Status
Price and basis
Notes
Hardware
Atmocube (US store)
Published price
USD 369.00, one-time, per device (United States store; shipping extra)
SKU not named on the store page; shown as sold out when checked. [12]
Hardware
Atmocube (EU store)
Published price
EUR 369.00, one-time, per device, taxes included (EU store (Austria shown))
Modbus-to-BACnet gateway (only if BACnet is needed)
Not publicly disclosed
—
Third-party Intesis gateway recommended; price not listed by Atmotech. [10]
Limitations and unresolved questions
Sensors differ by SKU: NOx is on BF2-E and BF2, CO and O3 only on BFCO2-E. Earlier SKUs are discontinued.
The REST API documentation did not render during review, so endpoints, history ranges and rate limits are unverified.
BACnet is not native; plan for a third-party gateway and its configuration.
The store showed the device as sold out on the date checked.
Conflicting or unclear documentation
The product FAQ describes optional cloud SaaS including REST API access, while the plans article limits API access to PRO and PRO+. [1, 4]
The product page lists 12 sensors without NOx, CO or O3; the SKU article assigns those to specific SKUs. The SKU article says “7 configurations” but lists eight SKUs. [1, 3]
Terms of use name Atmotech Inc.; terms of sale name Atmotube, Inc. The terms of use mention research use of APIs, while the terms of sale say data is for personal use. [14, 15]
Not yet answered by public documentation
Which SKU ships when you order, and does it carry the sensors you need?
What REST endpoints, history range and rate limits apply on PRO?
Is PRO priced per device in every region, and what happens to stored data if PRO lapses?
Do the data-use terms allow your intended use, especially any commercial reuse?
Before requesting a quote
Specify the exact SKU (BF2-E, BF2 or BFCO2-E) and confirm Ethernet/PoE if you need it.
Decide whether you will read data locally (Modbus/MQTT) or need the PRO cloud API.
Ask for the REST API reference and rate limits in writing before relying on it.
If BACnet is required, budget for the gateway and its configuration.
Ask what happens to cloud history if you move from PRO back to Basic.
Confirm stock and lead time; the store showed it as sold out when checked.
These are ordinary links to the manufacturer. The editor, Justin Carlson, co-founded and leads Invivus Technologies, which runs Moldmap, SensiReport and Moldlist and is developing Aerlume, an indoor mold sensor. He has no financial relationship with AirGradient, Airthings, Atmocube or Kaiterra, no vendor pays for coverage or placement, and the site has no affiliate links. Indoor Air API Guide does not provide manufacturer support.
Atmocube SKUs, Atmotech (specification). Checked November 7, 2026. Page date: October 15, 2025.
Cloud dashboard plans, Atmotech (pricing). Checked November 7, 2026. Page date: November 21, 2025.
Cloud dashboard API, Atmotech (documentation). Checked November 7, 2026. Page date: March 6, 2025.
Atmocube public API reference, Atmotech (documentation). Checked November 7, 2026. Page returned only a title during review (likely rendered client-side).