> For the complete documentation index, see [llms.txt](https://docs.uma.xyz/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.uma.xyz/resources/approved-price-identifiers.md).

# Approved Price Identifiers

This table includes identifiers that could be useful for new contracts and are likely to be encountered by proposers, disputers, and voters. It does not include identifiers that have been deprecated, identifiers that have fallen out of use, or specific token pairs.

If you need an identifier that is not included in this list, you can [submit a new UMIP](https://docs.umaproject.org/community/governance/the-umip-process) for approval. If a price request is made with an identifier that is not on this table, please refer to the canonical [UMIP directory](https://github.com/UMAprotocol/UMIPs/tree/master/UMIPs) on GitHub. The absence of an identifier from this table does *not* necessarily mean the identifier is not approved, it just means it is not recommended for new contracts.

If you want to use an approved identifier that is not on this list, let us know and we can add the identifier back to this table for easier voter/disputer reference.

<table><thead><tr><th width="290"></th><th width="333"></th><th></th></tr></thead><tbody><tr><td>ACROSS-V2</td><td>Verification of whether a bundle of Across bridge transactions submitted to mainnet is valid.</td><td><a href="https://github.com/UMAprotocol/UMIPs/blob/master/UMIPs/umip-179.md">UMIP-179</a></td></tr><tr><td>ASSERT_TRUTH<br>(DEPRECATED as of Dec 15, 2025)</td><td>Former default price identifier for Optimistic Oracle V3</td><td><a href="https://github.com/UMAprotocol/UMIPs/blob/master/UMIPs/umip-170.md">UMIP-170</a></td></tr><tr><td>ASSERT_TRUTH2<br>(as of Dec 8, 2025)</td><td>New intended default price identifier for Optimistic Oracle V3</td><td><a href="https://github.com/UMAprotocol/UMIPs/pull/629/files">UMIP-191</a></td></tr><tr><td>MULTIPLE_CHOICE_QUERY</td><td>Allows requests with a predefined set of valid responses.</td><td><a href="https://github.com/UMAprotocol/UMIPs/blob/master/UMIPs/umip-181.md">UMIP-181</a></td></tr><tr><td>NUMERICAL</td><td>Returns a number value based on a question asked in the ancillary data.</td><td><a href="https://github.com/UMAprotocol/UMIPs/blob/master/UMIPs/umip-165.md">UMIP-165</a></td></tr><tr><td>ROPU_ETHx</td><td>Reflects violations of the MEV-policy committed by validators of the ETHx staking protocol</td><td><a href="https://github.com/UMAprotocol/UMIPs/blob/master/UMIPs/umip-177.md">UMIP-177</a></td></tr><tr><td>YES_OR_NO_QUERY</td><td>Returns an answer to a "yes or no" question.</td><td><a href="https://github.com/UMAprotocol/UMIPs/blob/master/UMIPs/umip-107.md">UMIP-107</a></td></tr></tbody></table>


---

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

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.uma.xyz/resources/approved-price-identifiers.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.