> For the complete documentation index, see [llms.txt](https://docs.alcor.exchange/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.alcor.exchange/alcor-swap/alcorswap-v2-price-oracles/expanding-price-availability-with-ram-purchase.md).
# Expanding Price Availability with RAM Purchase
To extend the availability of historical price data within the Alcor Price Oracle, users can purchase additional RAM. The cost of purchasing RAM is determined by the current market price on the EOSIO blockchain, which can vary based on supply and demand. To calculate the RAM required for the desired data availability period, users can use the following formula:
| RAM Required (in bytes) = Number of Observations \* Size of Each Observation |
| ---------------------------------------------------------------------------- |
For instance, if a user wishes to have the price data available for 3 hours and each observation requires 160 bytes of RAM, they would need to calculate:
| RAM Required = 160 bytes \* 3 hours \* 60 minutes \* 60 seconds = 1.728 MB.
WAX Token = 0.4073 \* 1728 = 703.81440000 WAX (with RAM price is 0.4073 WAX per KB)
|
| ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
Once users have determined the required RAM size, they can proceed with the RAM purchase process by following:
| Transfer WAX to the swap.alcor account with the memo: "addoraclerow#poolId". |
| ---------------------------------------------------------------------------- |
Additionally, users can easily track the number of observations they have purchased by reviewing their [**transaction history**](https://wax.bloks.io/transaction/8430511460ddd7232cd35461fe0088966e3d71346cf5f860dee168561dca0dba)
---
# 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.alcor.exchange/alcor-swap/alcorswap-v2-price-oracles/expanding-price-availability-with-ram-purchase.md?ask=&goal=
```
`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.