Billing of Actual Usage
Update:
Through this article, you can understand the details of the pay based on actual usage billing model for the RTM product, including the cost components, billing methods, billing rules, and billing examples.
Cost Components
The services provided by LiveData are divided into RTM fees and Advanced Feature fees, which include translation, content moderation, etc.
At the end of each calendar month, LiveData will calculate the fees based on the monthly usage of the project, where:
- RTM fees = RTM message count (including and API calls) x message unit price
Billing Start
Billing will start when the user begins using the service, and LiveData will start tracking the usage and initiate billing.
Billing Method
Billing based on message count:
- RTM fees = RTM message count (including actual messages sent and API calls) x message unit price
For specific details, please contact LiveData’s sales team for consultation.
Billing Rules
- For different types of messages, the specific billing rules are as follows:
Message Type
Description
Billing Rules
P2P Message
Point-to-point message transmission
Each message counts as 1
Message length is counted as 1 for every 1k, rounded up to the nearest 1k if less than 1k
Group Message
Message transmission within a group
Calculated based on the total number of members in the group (regardless of whether users are online or not).
Message length is counted as 1 for every 1k, rounded up to the nearest 1k if less than 1k
Room Message
Message transmission within a room
Calculated based on the number of online users in the room.
Message length is counted as 1 for every 1k, rounded up to the nearest 1k if less than 1k
- For different types of file messages, the specific billing rules are as follows:
Message Type
Description
Billing Rules
Image Messages
Voice Messages
Video Messages
File Messages
File type messages
Based on the file size of the message, each 5k is counted as 1, rounded up to the nearest 5k if less than 5k
- For API calls, the specific billing rules are as follows:
API Type
Description
Billing Coefficient
Session and Unread-related APIs
Including group, room, and P2P session list APIs (including unread message count and the latest message)
10
History Message-related APIs
Including group, room, and P2P history message list APIs
5
APIs involving persistent operations
Including setting user, group, and room data, adjusting group members, etc.
2
Other types of APIs
APIs that do not involve persistent operations
1
- Additional fees for data storage, the specific billing rules are as follows:
By default, RTM supports storing chat history for 7 days, and a maximum of 500 messages can be stored in a single conversation. If you need to increase these two configurations, the total monthly message count will be multiplied by a coefficient of 1.1 as the final billing quantity.
Through this article, you can understand the details of the pay based on actual usage billing model for the RTM product, including the cost components, billing methods, billing rules, and billing examples.
Cost Components
The services provided by LiveData are divided into RTM fees and Advanced Feature fees, which include translation, content moderation, etc.
At the end of each calendar month, LiveData will calculate the fees based on the monthly usage of the project, where:
- RTM fees = RTM message count (including and API calls) x message unit price
Billing Start
Billing will start when the user begins using the service, and LiveData will start tracking the usage and initiate billing.
Billing Method
Billing based on message count:
- RTM fees = RTM message count (including actual messages sent and API calls) x message unit price
For specific details, please contact LiveData’s sales team for consultation.
Billing Rules
- For different types of messages, the specific billing rules are as follows:
| Message Type | Description | Billing Rules |
|---|---|---|
| P2P Message | Point-to-point message transmission | Each message counts as 1 Message length is counted as 1 for every 1k, rounded up to the nearest 1k if less than 1k |
| Group Message | Message transmission within a group | Calculated based on the total number of members in the group (regardless of whether users are online or not). Message length is counted as 1 for every 1k, rounded up to the nearest 1k if less than 1k |
| Room Message | Message transmission within a room | Calculated based on the number of online users in the room. Message length is counted as 1 for every 1k, rounded up to the nearest 1k if less than 1k |
- For different types of file messages, the specific billing rules are as follows:
| Message Type | Description | Billing Rules |
|---|---|---|
| Image Messages Voice Messages Video Messages File Messages |
File type messages | Based on the file size of the message, each 5k is counted as 1, rounded up to the nearest 5k if less than 5k |
- For API calls, the specific billing rules are as follows:
| API Type | Description | Billing Coefficient |
|---|---|---|
| Session and Unread-related APIs | Including group, room, and P2P session list APIs (including unread message count and the latest message) | 10 |
| History Message-related APIs | Including group, room, and P2P history message list APIs | 5 |
| APIs involving persistent operations | Including setting user, group, and room data, adjusting group members, etc. | 2 |
| Other types of APIs | APIs that do not involve persistent operations | 1 |
- Additional fees for data storage, the specific billing rules are as follows:
By default, RTM supports storing chat history for 7 days, and a maximum of 500 messages can be stored in a single conversation. If you need to increase these two configurations, the total monthly message count will be multiplied by a coefficient of 1.1 as the final billing quantity.