> For the complete documentation index, see [llms.txt](https://peri-finance.gitbook.io/perifinance/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://peri-finance.gitbook.io/perifinance/development-resources/integrations/data.md). # PERI FINANCE HISTORICAL DATA ## Peri Finance Historical Data Peri Finance's historical data ca access using number of ways in future * Using calls on the Graph subgraphs * Using an Archive Node to fetch state at some block in the past * Using Query event logs on the Graph Subgraph * Using Third party service like Google BigQuery ## The Graph and Subgraph To Query Network Data from Decentralized Network , Peri Finance has indexed protocol data on the Graph. The Graph allows for the creation of custom data sets called Subgraph , which allowed to be queryable. Peri Finance currently has One separate subgraphs for retrieving information specific to Peri Finance smart contracts. A subgraph is an entity-based data source which replays all transactions since the genesis block and uses custom code to create queryable entities as each block is processed. Alternatively, each of these subgraphs can be queried using GraphQL. ## Event Logs Query Instead of using the subgraphs provided, you could directly query the EVM via most free providers (such as Infura ). ## Using an Archive Node You can also use an Network(Polygon/Ethereum/BSC) node with full historical state to read the blockchain state at some block in the past. --- # 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://peri-finance.gitbook.io/perifinance/development-resources/integrations/data.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.