> For the complete documentation index, see [llms.txt](https://docs.aces.fun/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.aces.fun/the-aces-ratio.md). # The ACES Ratio How do you price an asset whose value is 90% narrative? Traditional metrics fail. So we architected a new one. Introducing The ACES Ratio - A real-time index of cultural hype. Simply put, the P/E ratio for a grail. This is where premium collectible RWAs change forever. While auction houses use lagging data (final sales), the ACES Ratio creates a leading indicator. A live feed of market sentiment and momentum. Christie's sees what sold. We see what's surging. This ratio gives us predictive power over which assets will perform and which cultural trends are about to break. Auction houses will pay for this data because we give them what they don’t have: real-time attention, sentiment, and momentum data to architect better auctions before anything sells. The realtime hype index ranks all listed collectibles against the collectible separating its market value to its hype value. This means items that may be listed at lower market caps, trade a premium because there is more hype behind the asset. By giving each asset an ACES ratio, anyone can list a high performing collectible. ![](/files/0X8o5ZgUB8trcgzl74sA) --- # 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.aces.fun/the-aces-ratio.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.