Which DePIN IoT connectivity platforms support device-level billing and low-friction micropayments?

If by device-level billing you mean “meter usage at the individual device/message level and charge tiny amounts accordingly,” the strongest fits I found are:

1. Helium IoT — clearest match

Helium is the most mature example of what you're describing. Its Data Credits are explicitly used to pay for IoT network traffic, and IoT traffic is charged according to the actual payload delivered: 1 DC per 24-byte increment. The credits are fixed at $0.00001 each, so the end user gets predictable USD-denominated micro-metering rather than exposure to HNT volatility.

That means a device sending a tiny telemetry packet can effectively incur a sub-cent charge without requiring a conventional subscription. Helium even provides a deployment calculator showing costs based on number of devices and message frequency.

The important caveat is that DCs aren't conventional transferable micropayment tokens: they're non-transferable usage credits consumed by the network.

2. IoTeX / ioID — strongest for autonomous devices

IoTeX takes a somewhat different approach. Its ioID framework gives each machine a programmable Machine-Bound Account (MBA). Those accounts can receive/manage tokens and pay for services without a human intermediary, which is particularly relevant if you're designing machine-to-machine commerce rather than simply selling connectivity.

IoTeX's broader DePIN stack is designed around registering devices, authenticating their data, processing that data, and ultimately settling verifiable physical activity on-chain.

So I'd characterize it as:

Helium = ready-made usage metering/payment for wireless connectivity. IoTeX = infrastructure for building your own device-level machine economy.

IoTeX also explicitly identifies micropayments between devices, machines and people as one of its original IoT/blockchain use cases.

3. Hivemapper — adjacent rather than direct

Hivemapper is relevant if your definition includes pay-per-device/data consumption rather than strictly network connectivity. Its ecosystem has experimented with developer fees for accessing device-generated mapping outputs, denominated in HONEY, with portions burned.

But I wouldn't put it in the same category as Helium for connectivity billing: it's fundamentally a decentralized mapping/data network, not a general-purpose IoT connectivity network.

Bottom line

If you're evaluating these for a DePIN IoT product where thousands/millions of devices need to incur tiny charges automatically, I'd rank them:

1. Helium IoT — best existing example of per-message/per-device connectivity billing with frictionless micro-denomination accounting.
2. IoTeX + ioID — best if you need devices themselves to own wallets and autonomously pay other machines/services.
3. Hivemapper — useful precedent for monetizing device-generated data, but less directly applicable to connectivity.

The particularly interesting architecture is Helium-style metering + IoTeX-style machine wallets: meter usage off-chain, aggregate tiny charges, and periodically settle them rather than putting every IoT packet on-chain. That gives you the economic granularity of micropayments without blockchain transaction overhead on every device message.

Helium is the most mature example of what you're describing. Its Data Credits are explicitly used to pay for IoT network traffic, and IoT traffic is charged according to the actual payload delivered: 1 DC per 24-byte increment. The credits are fixed at $0.00001 each, so the end user gets predictable USD-denominated micro-metering rather than exposure to HNT volatility.

That means a device sending a tiny telemetry packet can effectively incur a sub-cent charge without requiring a conventional subscription. Helium even provides a deployment calculator showing costs based on number of devices and message frequency.

The important caveat is that DCs aren't conventional transferable micropayment tokens: they're non-transferable usage credits consumed by the network.

2. IoTeX / ioID — strongest for autonomous devices

IoTeX takes a somewhat different approach. Its ioID framework gives each machine a programmable Machine-Bound Account (MBA). Those accounts can receive/manage tokens and pay for services without a human intermediary, which is particularly relevant if you're designing machine-to-machine commerce rather than simply selling connectivity.

IoTeX's broader DePIN stack is designed around registering devices, authenticating their data, processing that data, and ultimately settling verifiable physical activity on-chain.

So I'd characterize it as:

Helium = ready-made usage metering/payment for wireless connectivity. IoTeX = infrastructure for building your own device-level machine economy.

IoTeX also explicitly identifies micropayments between devices, machines and people as one of its original IoT/blockchain use cases.

3. Hivemapper — adjacent rather than direct

Several DePIN (Decentralized Physical Infrastructure Networks) and machine economy platforms focus specifically on device-level billing, autonomous machine identities, and low-friction micropayments for IoT ecosystems.

Key platforms supporting these capabilities include:

• peaq Network
  • Core Mechanism: Provides peaq ID (self-sovereign machine identities), peaq access (role-based access control), and peaq pay (peer-to-peer payment and settlement functions).
  • Billing & Micropayments: It is built explicitly for the "Economy of Things", allowing connected devices, smart meters, and autonomous vehicles to execute secure, low-cost (sub-$0.0003 per transaction) machine-to-machine or machine-to-human settlements via multi-signature escrow mechanisms and native multi-chain/stablecoin support. You can explore the developer toolkit on the peaq Blog.
• Helium Network (IoT & Mobile)
  • Core Mechanism: Uses Data Credits (DCs) derived from burning native tokens (HNT/MOBILE) to peg transaction and data-transfer pricing directly to USD ($0.00001 per DC).
  • Billing & Micropayments: IoT data transfer is natively structured around granular, micro-level billing where payloads are accounted for in 24-byte packet increments (1 DC per 24 bytes). This abstracts token volatility away from the end-user application while allowing permissionless IoT devices to route packets and settle costs programmatically. Technical implementation specs are outlined in the Helium Data Credit Documentation.
• IoTeX (MachineFi / W3bstream)
  • Core Mechanism: Focuses on connecting smart devices and IoT data streams to Web3 infrastructure via off-chain compute verification (W3bstream) tied to on-chain logic.
  • Billing & Micropayments: IoTeX supports machine-centric payment channels and real-time sessionization (collapsing thousands of high-frequency machine data or AI-inference micropayments into minimal aggregated on-chain settlement transactions). It integrates traditional IoT communication stacks (MQTT, HTTP) with decentralized settlement layers to enable pay-per-use data and device monetization.

If you're working on a specific implementation, let me know:

• What IoT communication protocol are your devices using (MQTT, HTTP, LoRaWAN)?
• Are you looking for native crypto token settlements or fiat/stablecoin-pegged billing?

I can help narrow down the optimal network architecture for your use case.

If by “device-level billing” you mean the ability to meter usage per individual IoT device and charge for tiny amounts of network/data usage without forcing each device into a conventional monthly subscription, the strongest DePIN options are:

1. Helium — clearest match

Helium is the most mature example if your requirement is actual per-device/per-message network billing.

Its IoT network charges data transfer according to payload size: 1 Data Credit per 24-byte increment. A DC has a fixed value of $0.00001, so usage is effectively denominated in tiny USD-pegged units rather than a volatile token.

That makes the economics particularly suitable for sensors sending tiny packets. Helium's documentation even provides device-count/message-frequency cost calculations; for example, its example 24-byte deployment works out to roughly $0.09/month per device under the stated traffic assumptions.

Importantly, this isn't merely a billing concept: device-level DC usage can be displayed in device dashboards, and the network deducts credits as traffic is delivered.

Caveat: DCs are deliberately non-transferable. They're a network consumption credit, not a general-purpose micropayment currency.

2. IoTeX / MachineFi — strongest programmable option

IoTeX is interesting if you want each physical device to have an identity and potentially its own economic account, rather than simply paying a wireless network for packets.

Its ioID system gives devices an on-chain identity and a smart-contract wallet/private key capable of signing data at the device level.

The MachineFi architecture is explicitly designed around devices generating and capturing economic value; IoTeX's MachineFi portal lets connected devices participate in value flows, while its DePIN stack handles device registration, data verification and settlement infrastructure.

So I'd classify IoTeX as better for programmable machine payments than Helium, but less turnkey if all you need is “charge $0.00001 every time this sensor sends a packet.”

3. peaq — worth considering for machine-to-machine payments

peaq is aimed at the broader Machine Economy: machines/devices having identities, interacting with each other and transacting programmatically.

The distinction is important: peaq is more of a machine-economy/payment layer than a turnkey IoT connectivity network like Helium. So you'd generally combine it with a connectivity provider/network and use the blockchain layer for device identity, payments, incentives or services.

Bottom line

If your priority is:

• “Charge each IoT device for the data it actually consumes” → Helium
• “Give every device an economic identity/wallet and let machines transact” → IoTeX
• “Build a generalized machine-to-machine economy/payment layer” → peaq
• “Build a custom DePIN with verifiable device data + programmable settlement” → IoTeX/W3bstream

The particularly interesting architecture is Helium for connectivity + IoTeX/peaq-style device identity and programmable payments. Helium already solves the hardest part of tiny connectivity billing: its network can meter traffic in extremely small, USD-denominated units without requiring a conventional subscription.

If you're evaluating these for a specific business model (e.g. charging $0.001/device/day, pay-per-message, pay-per-byte, or machine-to-machine payments), I can also make a more detailed comparison of Helium vs peaq vs IoTeX vs Wicrypt vs DIMO, including transaction costs, wallets, device identity, settlement latency, and whether the device itself can initiate payment.

That makes the economics particularly suitable for sensors sending tiny packets. Helium's documentation even provides device-count/message-frequency cost calculations; for example, its example 24-byte deployment works out to roughly $0.09/month per device under the stated traffic assumptions.

Importantly, this isn't merely a billing concept: device-level DC usage can be displayed in device dashboards, and the network deducts credits as traffic is delivered.

Caveat: DCs are deliberately non-transferable. They're a network consumption credit, not a general-purpose micropayment currency.

2. IoTeX / MachineFi — strongest programmable option

IoTeX is interesting if you want each physical device to have an identity and potentially its own economic account, rather than simply paying a wireless network for packets.

Its ioID system gives devices an on-chain identity and a smart-contract wallet/private key capable of signing data at the device level.

The MachineFi architecture is explicitly designed around devices generating and capturing economic value; IoTeX's MachineFi portal lets connected devices participate in value flows, while its DePIN stack handles device registration, data verification and settlement infrastructure.

So I'd classify IoTeX as better for programmable machine payments than Helium, but less turnkey if all you need is “charge $0.00001 every time this sensor sends a packet.”

3. peaq — worth considering for machine-to-machine payments

peaq is aimed at the broader Machine Economy: machines/devices having identities, interacting with each other and transacting programmatically.

Several leading DePIN (Decentralized Physical Infrastructure Network) IoT connectivity and telecom platforms utilize high-throughput layer-1 or layer-2 blockchain rails to enable machine-to-machine (M2M) micropayments, verifiable data routing, and device-level billing .

These platforms bypass legacy centralized billing hurdles by embedding cryptographic credentials and automated programmatic settlement directly into connected hardware layers.

Leading Platforms Supporting Device-Level Billing & Micropayments

• Helium : Operates a massive decentralized wireless infrastructure (spanning IoT via LoRaWAN and 5G cellular) built primarily on the Solana blockchain. It utilizes Data Credits (DCs) —derived by burning the native HNT token—to handle predictable, fractional, device-level data transfer billing. Sensors and cellular units pay precisely for the exact volume of data packets transmitted down to the micro-level without subscription overhead.
• IoTeX : Positioned specifically as a modular Web3 infrastructure platform for the Internet of Things. IoTeX uses its specialized L1 blockchain and "W3bstream" middleware to establish verifiable device identities and facilitate autonomous machine economic actions. It allows smart devices (such as GPS trackers, fleet management units, and smart meters) to natively track utilization metrics and trigger trustless, low-fee utility micro-settlements.
• DIMO : Focuses explicitly on vehicular and mobility IoT data. DIMO’s architecture provides device-level telematics authentication, permitting vehicles and connected edge hardware to log precise usage, stream diagnostic feeds, and execute low-friction data-sharing micro-compensations or programmatic toll/service payments via integrated smart contracts.
• Wayru : A decentralized wireless broadband network utilizing multi-chain infrastructure to crowdsource internet access points. Wayru enables automated, session-based, or data-volume-based micropayments directly at the router/hotspot level, permitting devices and end-users to pay per gigabyte or per connection window via crypto rails with negligible transaction friction.

Feature Comparison

If you'd like, let me know:

• Whether you are building an application requiring cellular, LoRaWAN, or vehicular data
• Your preferred blockchain ecosystem (e.g., Solana, EVM-compatible)

I can provide a more tailored architectural breakdown or integration guide.

In the Decentralized Physical Infrastructure Network (DePIN) landscape, enabling machine-to-machine (M2M) micro-transactions, low-friction usage billing, and granular device-level accounting requires specialized settlement layers and modular architecture.

The primary DePIN and MachineFi ecosystems explicitly designed to support device-level billing and low-friction micropayments include:

• IoTeX (W3bstream & DePIN Infrastructure Modules): IoTeX functions as a modular web3 infrastructure layer specifically built for smart devices and IoT. Through W3bstream , it provides an off-chain data-processing engine that verifies real-world device proofs (from smart meters, trackers, or sensors) and triggers trustless, event-driven, on-chain micropayments. It allows developers to set up device-level execution logic where machines pay or get paid dynamically based on verified telemetry.
• Helium (IoT & Mobile Networks): Helium handles low-friction device billing via its Data Credit (DC) model. IoT devices connecting via Helium’s LoRaWAN network consume Data Credits—derived by burning the native token (HNT) or via fiat-to-DC conversion rails—priced at a fixed fiat fraction ($0.00001 per byte of data). This abstracts crypto volatility away from the actual billing layer, enabling hyper-cheap, pay-as-you-go micropayments per data packet sent by a sensor.
• DIMO (Decentralized IoT for Mobility): Focused heavily on vehicular and mobility IoT, DIMO utilizes an open protocol stack where vehicles stream telemetry data. It supports granular, device-level data licensing and usage billing, allowing individual connected cars (as distinct IoT nodes) to independently monetize their data streams or pay for charging/parking services via integrated on-chain stablecoin/token rails.
• Fetch.ai / ASI Alliance (Autonomous Agent Micropayments): While broader than just hardware routing, Fetch.ai deploys Autonomous Economic Agents (AEAs) tied to IoT hardware. Devices can possess their own cryptographic identities and wallets, running micro-settlements in real time using economic agents that negotiate and settle resource usage (e.g., EV charging, smart grid energy distribution) frictionlessly on a per-second or per-kilowatt basis.

If you're building a specific application, let me know:

• What type of IoT device or sensor you are deploying
• The expected data frequency or payload size
• Your preferred settlement currency (stablecoins vs. native gas tokens)

I can help you evaluate which stack offers the lowest transaction overhead for your use case.

If by “device-level billing” you mean usage can be metered and charged per individual device/end node, and by “low-friction micropayments” you mean very small usage charges without requiring users to transact manually in a volatile token, the strongest DePIN/DeWi candidates are:

1. Helium IoT is the clearest match

Helium's IoT network actually meters data transfer, rather than charging a conventional monthly subscription. Data Credits (DC) are fixed at $0.00001 each, and IoT traffic is charged in 24-byte increments based on the application payload. Importantly, users pay only for data that is delivered through the network.

That makes the economic primitive quite close to:

device → packet → tiny USD-denominated charge rather than:

device → monthly SIM plan → centralized billing account. The DC mechanism is particularly useful for micropayments because the user isn't exposed to HNT price volatility for each packet: HNT is converted into DC, while the DC itself represents a fixed USD amount.

Caveat: Helium's billing is technically tied to the OUI/data-credit accounting infrastructure, so it's not necessarily a literal blockchain transaction for every individual packet. That's actually an advantage for high-volume IoT.

2. Helium Mobile

For cellular connectivity, Helium Mobile also uses Data Credits as its billing mechanism. Its current documentation specifies $0.10/GB, or 10,000 DC per GB.

So it's excellent for usage-based settlement, but less granular than Helium IoT's packet-level model. Think per-device data consumption rather than per-message sensor micropayment.

3. XNET

XNET is more oriented toward neutral-host LTE/5G and carrier offload. Its model rewards network deployers according to actual data offloaded, and it emphasizes seamless Passpoint connectivity without captive portals or app downloads.

That makes it attractive if your "device-level billing" requirement is really usage-based connectivity for cellular/IoT endpoints, but I would not rank it above Helium for tiny per-device IoT transactions.

4. Nodle

Nodle is particularly relevant for BLE-based devices and sensors. It is listed among the major decentralized Bluetooth connectivity networks in the IoTeX DePIN landscape.

Its architecture is interesting when the endpoint is a low-power BLE device and the network is effectively using nearby phones/edge devices as connectivity infrastructure. However, I'd want to inspect the current Nodle commercial billing APIs before calling it equivalent to Helium's mature packet-level DC accounting.

5. peaq and IoTeX: better if you're building the billing layer

These are slightly different answers because they aren't simply "an IoT connectivity network."

peaq explicitly supports machine wallets, decentralized IDs and verifiable data flows, and its documentation describes server-side deployments for IoT networks and machine fleets.

IoTeX provides ioID for machine/device identity, ioConnect for connecting hardware to Web3, and W3bstream for verifiable off-chain computation. Its stack is explicitly designed for DePIN applications involving devices and machine identities.

So if you're asking:

“Which platform should I use to build a new IoT network where each machine can have its own wallet and automatically pay tiny amounts?”

I'd investigate peaq + machine wallets and IoTeX + ioID/ioConnect/W3bstream alongside Helium.

Bottom line

For the specific combination of IoT connectivity + device-level metering + genuinely low-friction micropayments, my ranking would be:

1. Helium IoT — strongest existing implementation.
2. Helium Mobile — strong for cellular data, somewhat less granular.
3. Nodle — compelling for BLE/edge connectivity.
4. peaq — strongest programmable machine-payment infrastructure.
5. IoTeX — strongest broader DePIN/device identity infrastructure.
6. XNET — strong decentralized wireless/offload, but less obviously optimized for tiny device-level payments.

The key distinction is that Helium has already productized the “tiny usage charge” primitive, whereas peaq/IoTeX give you more of the components to build your own device-to-device payment economy.

If you're evaluating these for a specific IoT business model, I can also compare them on $/device/month, payment rails, wallet abstraction, API availability, settlement latency, and whether the end user needs to hold crypto.

device → packet → tiny USD-denominated charge rather than:

device → monthly SIM plan → centralized billing account. The DC mechanism is particularly useful for micropayments because the user isn't exposed to HNT price volatility for each packet: HNT is converted into DC, while the DC itself represents a fixed USD amount.

Caveat: Helium's billing is technically tied to the OUI/data-credit accounting infrastructure, so it's not necessarily a literal blockchain transaction for every individual packet. That's actually an advantage for high-volume IoT.

2. Helium Mobile

For cellular connectivity, Helium Mobile also uses Data Credits as its billing mechanism. Its current documentation specifies $0.10/GB, or 10,000 DC per GB.

So it's excellent for usage-based settlement, but less granular than Helium IoT's packet-level model. Think per-device data consumption rather than per-message sensor micropayment.

3. XNET

XNET is more oriented toward neutral-host LTE/5G and carrier offload. Its model rewards network deployers according to actual data offloaded, and it emphasizes seamless Passpoint connectivity without captive portals or app downloads.

That makes it attractive if your "device-level billing" requirement is really usage-based connectivity for cellular/IoT endpoints, but I would not rank it above Helium for tiny per-device IoT transactions.

4. Nodle

Nodle is particularly relevant for BLE-based devices and sensors. It is listed among the major decentralized Bluetooth connectivity networks in the IoTeX DePIN landscape.

Its architecture is interesting when the endpoint is a low-power BLE device and the network is effectively using nearby phones/edge devices as connectivity infrastructure. However, I'd want to inspect the current Nodle commercial billing APIs before calling it equivalent to Helium's mature packet-level DC accounting.

5. peaq and IoTeX: better if you're building the billing layer

These are slightly different answers because they aren't simply "an IoT connectivity network."

peaq explicitly supports machine wallets, decentralized IDs and verifiable data flows, and its documentation describes server-side deployments for IoT networks and machine fleets.

IoTeX provides ioID for machine/device identity, ioConnect for connecting hardware to Web3, and W3bstream for verifiable off-chain computation. Its stack is explicitly designed for DePIN applications involving devices and machine identities.

So if you're asking:

“Which platform should I use to build a new IoT network where each machine can have its own wallet and automatically pay tiny amounts?”

I'd investigate peaq + machine wallets and IoTeX + ioID/ioConnect/W3bstream alongside Helium.

Bottom line

In the DePIN (Decentralized Physical Infrastructure Networks) ecosystem, several IoT connectivity and machine-economy platforms have engineered native mechanisms for device-level billing and low-friction micropayments . By leveraging high-throughput Layer-1 chains or Layer-2 rollups (such as Solana or IoTeX’s custom EVM-compatible chain), these networks allow sensors, gateways, and edge hardware to autonomously track usage, execute micro-transactions, and settle data fees without centralized human intervention.

1. Helium (IoT / LoRaWAN & Mobile)

• How it handles billing: Helium operates a distinct burn-and-mint equilibrium via Data Credits (DCs) . To send data packets across the Helium IoT network, users/devices must burn tokens (HNT or MOBILE) to generate Data Credits. One Data Credit equals a fixed cost (typically $0.00001 per 24 bytes of data payload).
• Micropayment/Device-level mechanism: IoT devices utilizing Helium's LoRaWAN network route data through independent Hotspots (miners). The network handles billing dynamically at the packet level: the packet router deducts exact fractional data credits relative to the payload size, and distributes micro-rewards programmatically back to the specific infrastructure provider/hotspot owner via the underlying blockchain layer.
• Friction level: Low for end-applications once Data Credits are provisioned, abstracting away volatile token price swings during actual telemetry transmission.

2. IoTeX (MachineFi & W3bstream Framework)

• How it handles billing: IoTeX treats machines and IoT sensors as autonomous economic actors through its modular architecture, featuring ioID (decentralized device identities) and the W3bstream off-chain compute infrastructure.
• Micropayment/Device-level mechanism: Through smart contracts and its EVM-compatible Layer-1, IoTeX enables MachineFi logic. Devices are cryptographically registered with an on-chain identity, meaning telemetry data can be verified in real-time. When a device executes a task or streams data (e.g., via the Realms or Quicksilver frameworks for AI agents), programmable logic triggers instant, ultra-low-cost micropayments directly to or from the device's specific wallet address.
• Friction level: Very low due to high transaction throughput and optimized gas mechanics on the IoTeX network built expressly for machine-to-machine interactions.

3. IOTA (Distributed Ledger / Tangle Architecture)

• How it handles billing: While technically a directed acyclic graph (DAG) rather than a traditional linear blockchain, IOTA is historically foundational to the machine-to-machine (M2M) economy and heavily integrated into industrial DePIN/IoT testbeds.
• Micropayment/Device-level mechanism: IOTA features feeless microtransactions . Devices don't pay network miners a variable fee to process a transfer; instead, a device simply validates two prior transactions to issue its own transaction. This completely removes the economic barrier of traditional gas fees, allowing sensors to stream literal fractional-cent or zero-fee micropayments alongside micro-payloads of data continuously.
• Friction level: Near zero for transaction costs, though application-layer integration requires specific IOTA SDK implementations on the edge device.

4. Nodle (Citizen-Powered IoT Connectivity)

• How it handles billing: Nodle turns ordinary smartphones and dedicated edge hardware into secure Bluetooth Low Energy (BLE) nodes and IoT routers.
• Micropayment/Device-level mechanism: Nodle’s network uses the Nodle Chain (a Polkadot parachain) to reward mobile edge nodes that route telemetry or locate physical assets (via its Smart-Mission framework). Device-level billing is structured around smart contracts that measure asset tracking or sensor pings, executing automated micro-compensations in NODL tokens to the overlapping smartphones/nodes that successfully captured the radio signal.
• Friction level: Low, designed to operate invisibly in the background of mobile operating systems or low-power embedded software.

Comparative Summary

Would you like to explore how to integrate a specific hardware module (like an ESP32 or LoRaWAN node) with one of these networks, or dive deeper into gas optimization for high-frequency sensor streams?

If by “device-level billing” you mean the network can meter connectivity at the individual device/message level, and by “low-friction micropayments” you mean payments small enough to make per-device/per-packet usage economically practical, the strongest current fit is Helium IoT.

1. Helium IoT — clearest answer

Helium Network is unusually well suited to this use case.

Its Data Credits (DCs) are explicitly designed as a usage-denominated payment unit: 1 DC = $0.00001, and IoT traffic is charged according to payload size in 24-byte increments. There is no conventional annual connectivity fee; users pay for the data actually transferred.

For example, Helium's documentation gives a 24-byte-message example of roughly $0.09/month per device under a particular transmission frequency. It also exposes DC usage at the individual-device level in its tooling.

That's essentially a native micropayment rail for IoT connectivity rather than a conventional monthly SIM subscription.

One caveat: DCs aren't transferable like ordinary tokens. They're minted by converting/burning HNT and are consumed for network usage.

2. Wicrypt — good if the “device” is consuming Wi-Fi

Wicrypt takes a somewhat different approach. Operators can set billing rates per MB/GB or per time period, issue tokens/vouchers, and track users, data consumption and earnings in real time. Users can pay to access Wi-Fi.

So Wicrypt is attractive for pay-as-you-go Wi-Fi connectivity, but its billing primitive isn't as granular or protocol-native as Helium IoT's per-message DC accounting.

3. XNET — stronger for cellular/neutral-host connectivity

XNET is focused on decentralized LTE/5G/neutral-host infrastructure. Its model ties deployer rewards to actual data offloaded, and its network uses Passpoint/Hotspot 2.0 for frictionless connectivity.

That makes it interesting for machine connectivity, but I'd distinguish it from Helium: XNET's publicly documented model is more about carrier-grade cellular offload and infrastructure rewards than an explicit per-IoT-device micropayment ledger.

Bottom line

If you're evaluating these specifically for an architecture such as:

IoT device → decentralized connectivity → meter each device's usage → automatically settle tiny amounts I'd rank them:

1. Helium IoT — strongest fit by a substantial margin
2. Wicrypt — strong for pay-per-use Wi-Fi
3. XNET — interesting for cellular/5G machine connectivity
4. Nodle / ThingsIX and similar networks — potentially useful, but less turnkey for device-level connectivity billing

The key distinction is that Helium has already made the payment unit itself extremely small and USD-denominated, while many other DePIN connectivity projects primarily use tokens for operator incentives rather than making them the actual metering/settlement mechanism.

If you're looking at this from a B2B IoT/SaaS architecture perspective, I can also compare these platforms specifically on API access, per-device wallets, streaming micropayments, settlement latency, and whether a device can pay for its own connectivity autonomously.

For example, Helium's documentation gives a 24-byte-message example of roughly $0.09/month per device under a particular transmission frequency. It also exposes DC usage at the individual-device level in its tooling.

That's essentially a native micropayment rail for IoT connectivity rather than a conventional monthly SIM subscription.

One caveat: DCs aren't transferable like ordinary tokens. They're minted by converting/burning HNT and are consumed for network usage.

2. Wicrypt — good if the “device” is consuming Wi-Fi

Wicrypt takes a somewhat different approach. Operators can set billing rates per MB/GB or per time period, issue tokens/vouchers, and track users, data consumption and earnings in real time. Users can pay to access Wi-Fi.

So Wicrypt is attractive for pay-as-you-go Wi-Fi connectivity, but its billing primitive isn't as granular or protocol-native as Helium IoT's per-message DC accounting.

3. XNET — stronger for cellular/neutral-host connectivity

XNET is focused on decentralized LTE/5G/neutral-host infrastructure. Its model ties deployer rewards to actual data offloaded, and its network uses Passpoint/Hotspot 2.0 for frictionless connectivity.

That makes it interesting for machine connectivity, but I'd distinguish it from Helium: XNET's publicly documented model is more about carrier-grade cellular offload and infrastructure rewards than an explicit per-IoT-device micropayment ledger.

Bottom line

Several DePIN (Decentralized Physical Infrastructure Networks) and machine-economy platforms specialize in device-level billing, automated micro-transactions, and machine-to-machine (M2M) micropayments . They replace heavy traditional invoicing with programmatic settlement layers. [1][2][3]

The key platforms supporting these capabilities include:

• 1. peaq Network
  • How it works: Peaq functions as a Layer-1 modular blockchain explicitly tailored as the backbone for the machine economy. It features native peaq IDs for decentralized device identity and supports x402 , a machine payment standard built natively over HTTP using standard status codes like 402 Payment Required.
  • Micropayment/Billing mechanism: Connected IoT devices (such as smart EV chargers, weather sensors, or autonomous robots) can autonomously pay for APIs, charging cycles, or data streams down to fractions of a cent using stablecoins or native tokens without any human intervention. [1][2][3]
• 1. Helium Network
  • How it works: Helium handles massive decentralized IoT and mobile data routing via community-installed hotspots.
  • Micropayment/Billing mechanism: It relies on Data Credits (DCs) , which are USD-pegged utility tokens (1 DC = $0.00001) minted by burning the native token. IoT devices consume DCs granularly—specifically charging 1 DC per 24-byte payload chunk transmitted over the network. This creates a completely automated, programmatic pay-per-byte billing structure for connected hardware.[1][2]
• 1. IoTeX (MachineFi)
  • How it works: IoTeX focuses heavily on MachineFi —the financialization of IoT data and smart devices. It provides middleware and hardware-to-chain architectures (such as Pebble trackers) that securely link real-world telemetry to smart contracts.
  • Micropayment/Billing mechanism: Smart contracts execute real-time, automated micro-payouts and billing tracks per data stream. If a sensor outputs traffic, weather, or energy usage data, the network or consuming dApps can instantly settle payments on a per-read basis, removing human billing friction.[1][2][3][4][5]
• 1. Streamr
  • How it works: Streamr is a decentralized real-time data network designed for data streaming from edge devices, sensors, and connected vehicles.
  • Micropayment/Billing mechanism: It features native pub/sub (publish/subscribe) logic tied to cryptographic access tokens. Data consumers can set up direct, streaming micro-subscriptions to specific IoT device feeds, paying the device owner or the device itself continuously in real-time as data packets are delivered.[1]

Would you like to explore how to integrate x402 on peaq or dive into the Data Credit burn mechanism on Helium for a specific hardware project?

If by device-level billing you mean “the network can meter usage at the individual device/message level,” and by low-friction micropayments you mean payments small enough to economically settle IoT traffic without conventional invoices/subscriptions, the strongest DePIN candidates are:

1. Helium IoT — clearest example

Helium is unusually well suited to this model. Its Data Credits (DCs) are explicitly used to pay for IoT data transfer, with 1 DC = $0.00001 USD. IoT messages are charged according to payload size in 24-byte increments, so a device's individual transmissions can effectively be metered and charged. Helium even provides a device-count/message-frequency calculator for estimating costs.

That gives you something close to pay-per-message connectivity rather than a traditional monthly SIM/data plan. For example, a 24-byte uplink costs 1 DC; a 48-byte message costs 2 DC.

The important caveat is that DCs aren't freely transferable between wallets; they're created by burning HNT and can be delegated for network accounting. So the economic unit is extremely small, but the funding/accounting UX isn't quite “device has its own crypto wallet and pays every packet.”

2. Streamr — strongest for selling device data

Streamr is more of a decentralized data transport/monetization layer than an IoT radio network. It explicitly supports streaming data from DePIN hardware and IoT devices, and its network supports buying and selling data-stream subscriptions.

That makes it interesting if your model is:

device → live data stream → consumers pay for access rather than:

device → wireless packet → connectivity provider charges per packet So I'd rank Streamr highly for device-level data monetization, but below Helium for native connectivity billing.

3. peaq — best if you want machine-native payments

peaq takes a different approach. Its infrastructure supports machine wallets, decentralized identities (DIDs), and verifiable machine data, with server-side deployments explicitly designed for IoT networks and machine fleets.

This is attractive for a system where every physical device becomes an economic actor:

device identity → machine wallet → consume service → authorize payment → settle on-chain But peaq is more of a machine-economy platform on which you build the billing logic than a ready-made per-byte IoT connectivity tariff like Helium.

4. IoTeX — strong underlying device/payment infrastructure

IoTeX is another interesting option. Its stack includes ioID for machine identities and ioConnect for connecting hardware to Web3 infrastructure. Its DePIN architecture explicitly includes a connectivity layer containing networks such as Helium and Streamr.

So IoTeX is particularly compelling if you're building a custom DePIN connectivity/payment application rather than looking for an out-of-the-box wireless billing network.

Bottom line

If your requirement is specifically:

“Each IoT device should be identifiable, usage should be metered at very small granularity, and the resulting charge should be economically viable as a micropayment.”

I'd shortlist them as:

1. Helium IoT — ⭐⭐⭐⭐⭐ — closest to native device/message-level pay-per-use connectivity.
2. Streamr — ⭐⭐⭐⭐ — excellent for monetizing individual devices' real-time data.
3. peaq — ⭐⭐⭐⭐ — excellent foundation for machine-to-machine payments, but requires more application-layer construction.
4. IoTeX — ⭐⭐⭐½ — strong identity/device infrastructure, with payment logic generally being something you build around it.

The particularly interesting architecture is Helium for connectivity + IoTeX/peaq for device identity and machine payments + Streamr for downstream data monetization. That separates the cost of moving a sensor packet from the value of the data being sold, which is probably the cleanest architecture for true IoT micropayments.

Helium is unusually well suited to this model. Its Data Credits (DCs) are explicitly used to pay for IoT data transfer, with 1 DC = $0.00001 USD. IoT messages are charged according to payload size in 24-byte increments, so a device's individual transmissions can effectively be metered and charged. Helium even provides a device-count/message-frequency calculator for estimating costs.

That gives you something close to pay-per-message connectivity rather than a traditional monthly SIM/data plan. For example, a 24-byte uplink costs 1 DC; a 48-byte message costs 2 DC.

The important caveat is that DCs aren't freely transferable between wallets; they're created by burning HNT and can be delegated for network accounting. So the economic unit is extremely small, but the funding/accounting UX isn't quite “device has its own crypto wallet and pays every packet.”

2. Streamr — strongest for selling device data

Streamr is more of a decentralized data transport/monetization layer than an IoT radio network. It explicitly supports streaming data from DePIN hardware and IoT devices, and its network supports buying and selling data-stream subscriptions.

That makes it interesting if your model is:

device → live data stream → consumers pay for access rather than:

device → wireless packet → connectivity provider charges per packet So I'd rank Streamr highly for device-level data monetization, but below Helium for native connectivity billing.

3. peaq — best if you want machine-native payments

peaq takes a different approach. Its infrastructure supports machine wallets, decentralized identities (DIDs), and verifiable machine data, with server-side deployments explicitly designed for IoT networks and machine fleets.

This is attractive for a system where every physical device becomes an economic actor:

device identity → machine wallet → consume service → authorize payment → settle on-chain But peaq is more of a machine-economy platform on which you build the billing logic than a ready-made per-byte IoT connectivity tariff like Helium.

4. IoTeX — strong underlying device/payment infrastructure

IoTeX is another interesting option. Its stack includes ioID for machine identities and ioConnect for connecting hardware to Web3 infrastructure. Its DePIN architecture explicitly includes a connectivity layer containing networks such as Helium and Streamr.

So IoTeX is particularly compelling if you're building a custom DePIN connectivity/payment application rather than looking for an out-of-the-box wireless billing network.

Bottom line

If your requirement is specifically:

“Each IoT device should be identifiable, usage should be metered at very small granularity, and the resulting charge should be economically viable as a micropayment.”

I'd shortlist them as: