> ## Documentation Index
> Fetch the complete documentation index at: https://docs.hyperx.dev/llms.txt
> Use this file to discover all available pages before exploring further.

# Cost and Usage

> Monitor project usage in Console and reduce excessive calls or storage.

The Console Billing page shows usage by organization and project. Usage is grouped by API calls, storage, CDN egress, game logs, push devices, and realtime usage.

## What to Watch

| Item           | Meaning                                        | How to Reduce It                                                    |
| -------------- | ---------------------------------------------- | ------------------------------------------------------------------- |
| API calls      | SDK and Web API request volume                 | Cache values repeatedly read on the same screen.                    |
| Storage bytes  | Public Storage and runtime data size           | Remove old files, unused save slots, and large JSON payloads.       |
| CDN egress     | Public Storage download traffic                | Check hashes and download only changed files.                       |
| Game logs      | `player.InsertGameLog` event volume            | Remove logs and payload fields that are not used operationally.     |
| Push devices   | Registered push tokens                         | Refresh stale tokens on logout, account switch, and token rotation. |
| Realtime usage | Notification/chat polling and acknowledgements | Stop polling when the screen is closed or increase intervals.       |

## Operating Procedure

1. Open Billing in Console.
2. Select the month and project.
3. Find the highest usage categories.
4. Review SDK call sites and Console settings for that feature.
5. Compare usage after the next aggregation cycle.

## Feature Tips

* Check hashes or versions before downloading public files or game configs.
* Call ranking `Top`, `Me`, and `AroundMe` only when the screen needs them.
* Standardize game log event names and payload schemas.
* Prefer the default user data record, create multiple records only when needed, and prune old large payloads first.
* Use short polling intervals only while realtime screens are foregrounded.

For billing commitments and included quota, use the latest plan shown in Console or your agreement.