> For the complete documentation index, see [llms.txt](https://docs.otherside.xyz/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.otherside.xyz/platform-documentation/admins/pricing/included-usage-and-overages.md).

# Included Usage & Overages

Each Virtual World Subscription includes a certain amount of free usage. If your project exceeds the included usage, overage charges will apply at the rates detailed below

### Provisioned Player Hours

Morpheus Platform uses the concept of Worlds - these are pre-configured templates of servers that support a certain player scale of virtual experience. In order to have users connect to your virtual experience, a World will need to be started that is running your content (aka "Mod"). There are many different sizes of worlds that can be spun up and they can be selected based on the expected number of players.

**Provisioned player hours** is the unit of usage for Morpheus Platform Worlds. If a World is spun up that can support 100 concurrent users for one hour, this would equate to 100 provisioned player hours of usage. Provisioned player hours are independent of the utilisation of those worlds (i.e. in this example it would be 100 provisioned player hours regardless of how many players were connected to the world during that time period).

### Bots (Simulated Players)

Bots can be used to simulate players within a world and identify any issues with load/ space layout (see page on [bots](https://docs.otherside.xyz/platform-documentation/creation/unreal-development/features-and-tutorials/bots.md) for more information).

Bots are priced at $0.01 per bot, per hour for all world sizes.

### Included Usage

The Basic platform subscription tier includes:

* 300,000 provisioned player hours
* 20,000 bot-hours

Both of these can be used across any of the world sizes up to the 5,000 capacity world.

Note: There are zero cloud streaming hours included in the Basic Tier subscription.

### Overage Charges

|                                                                                                        | Rate                              |
| ------------------------------------------------------------------------------------------------------ | --------------------------------- |
| Worlds                                                                                                 | $0.02 per provisioned player hour |
| [Cloud Streaming](https://docs.otherside.xyz/platform-documentation/admins/pricing/cloud-streaming.md) | $1.50 per stream-hour             |
| Bots                                                                                                   | $0.01 per bot-hour                |

There is no additional cost for connected users to the world template - this is already included.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.otherside.xyz/platform-documentation/admins/pricing/included-usage-and-overages.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
