> For the complete documentation index, see [llms.txt](https://docs.regionx.tech/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.regionx.tech/docs/advanced/dynamic-coretime-pricing.md).

# Dynamic Coretime pricing

The regions sold in the market are classified into two categories:

* Active regions. Active regions can be used in the current moment. This means that if we assign a task to an active region, it will start execution in the upcoming timeslice (assuming that the region doesn't begin later in the future)
* Inactive regions. These are the regions that will become active in the upcoming Bulk period. The regions purchased from the Coretime chain fall into this category until the start of the next Bulk period.

**Region pricing**

The formula used to calculate the price of a region listed for sale is as follows:

$$
r\_{price}=(r\_{end}- t)\*tp
$$

Where:

* $r\_{end}$: is the timeslice at which the region concludes
* $t$: represents the current timeslice
* $tp$: is the cost per timeslice defined by the seller upon listing the region on the market. Based on the region's core occupancy (which defines what portion of the core the region occupies), the timeslice price will likely differ.

> The parachain doesn't store the entire region's price; instead, it records the price of its timeslice, which is determined at the time of listing the region.

Through this, we are achieving dynamic pricing for 'active' regions which reflects their gradual loss of value when not being used.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.regionx.tech/docs/advanced/dynamic-coretime-pricing.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.