Usage and Billing
API usage is charged to the Producer's wallet. The billing model differs between Cloud Data (MongoDB) and Telemetry (InfluxDB).
Per-call charges
For both systems, each call to a read or write API is charged per call to the wallet. If the Producer has purchased a service package, one unit is deducted from the package's remaining service count instead.
| API | Database | Service type |
|---|---|---|
SendSMS | — | Charged to the wallet per receiver |
UpsertCloudData | MongoDB | Data add |
ReadCloudData | MongoDB | Data read |
AddTelemetryCloudData | InfluxDB | Data add |
ReadTelemetryCloudData | InfluxDB | Data read |
DeleteTelemetryCloudData | InfluxDB | No charge defined in the specification |
Daily storage billing
MongoDB (Cloud Data)
- The total daily storage cost is deducted from the Producer every day.
- Billing is based on the total size of the stored data.
- The system defines a data retention tariff per gigabyte: the cost of keeping 1 GB of data.
- Each day, the Producer's data size is calculated and charged according to that tariff.
InfluxDB (Telemetry)
- The total daily cost is deducted from the wallet every day.
- Billing is based on the number of stored data points, not on storage bytes.
- The data retention tariff is defined per point count.
Key difference
MongoDB storage is billed by size (GB). InfluxDB storage is billed by number of data points.
Deleted data and daily billing
Deleting data may not immediately reduce the size or point count used for billing, because the daily cost of that data must still be included in the daily calculation. The recorded usage for deleted data is reduced after the daily calculation and deduction have been completed.