# Overview
GrindURUS is an infrastructure protocol that provides tokenized access to liquidity and yield, generated from crypto market price volatility.
The protocol collect and allocate capital into custody smart-contract, that utilize inventory assets and swap aggregators for generating yield from price movements and distribute yield to liquidity providers.
#### Price volatility
Price volatility is the movement of an asset’s price over time.
Example:
The price of most cryptocurrnecies changes over time like:
* Day 1: $2000
* Day 2: $2200
* Day 3: $2100
or by seconds in orderbook or AMM
* second 1: $2000.03
* second 2: $2004.86
* second 3: $2002.32
These price changes represent volatility.
Even without a clear upward or downward trend, the movement between price levels creates opportunities for extracting yield.
#### Volatility Yield Generation
GrindURUS uses an Automated Market Taker (AMT) engine to generate yield from price volatility through buy low → sell high and sell high → buy low modes.
AMT treats positions as programmable state objects, enabling deterministic operations such as rebalancing and inventory management.
The AMT is accessed via the Grinder, which orchestrates execution and capital allocation through the Allocator.
#### Tokenomics
GRAI is a share-index token representing ownership in the GrindURUS system. Users deposit assets and receive GRAI proportional to total system value.
Yield is generated by automated trading (Grinder) and custody distributed between GRAI holders and the protocol.
---
# Agent Instructions: 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:
```
GET https://docs.grindurus.xyz/general/overview.md?ask=
```
The question should be specific, self-contained, and written in natural language.
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.