> 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/developers.md).

# Developers

- [ManagedOptimisticOracleV2](https://docs.uma.xyz/developers/managedoptimisticoraclev2.md)
- [Optimistic Oracle v2](https://docs.uma.xyz/developers/optimistic-oracle.md)
- [Using Blacklisting Tokens as Currency](https://docs.uma.xyz/developers/optimistic-oracle/using-blacklisting-tokens-as-currency.md)
- [Quick Start](https://docs.uma.xyz/developers/optimistic-oracle/getting-started.md): 0 to 1 Optimistic Oracle integration by example.
- [Deposit Box](https://docs.uma.xyz/developers/optimistic-oracle/solidity-examples.md): Simple deposit box example that showcases the basic request propose lifecycle of the UMA Optimistic Oracle
- [Event-Based Prediction Market](https://docs.uma.xyz/developers/optimistic-oracle/in-depth-tutorial-event-based-prediction-market.md): Building a prediction market that uses the UMA Optimistic Oracle for settlement and event identification
- [Insurance Claim Arbitration](https://docs.uma.xyz/developers/optimistic-oracle/in-depth-tutorial-insurance-claims-arbitration.md): Using the Optimistic Oracle to allow for verification of insurance claims
- [Internal Optimistic Oracle](https://docs.uma.xyz/developers/optimistic-oracle/internal-optimistic-oracle.md): Using the Optimistic Oracle to verify arbitrary data type results proposed through an external contract
- [Optimistic Arbitrator](https://docs.uma.xyz/developers/optimistic-oracle/in-depth-tutorial-optimistic-arbitrator.md): Wrapping Optimistic Oracle functionality into individual function calls
- [Optimistic Oracle v3](https://docs.uma.xyz/developers/optimistic-oracle-v3.md)
- [ASSERT\_TRUTH Deprecation](https://docs.uma.xyz/developers/optimistic-oracle-v3/assert_truth-deprecation.md)
- [Using Blacklisting Tokens as Currency](https://docs.uma.xyz/developers/optimistic-oracle-v3/using-blacklisting-tokens-as-currency.md)
- [Quick start](https://docs.uma.xyz/developers/optimistic-oracle-v3/quick-start.md): 0 to 1 integration with the Optimistic Oracle V3.
- [Prediction Market](https://docs.uma.xyz/developers/optimistic-oracle-v3/prediction-market.md): Building a prediction market that uses the UMA Optimistic Oracle V3 for settlement and event identification
- [Insurance](https://docs.uma.xyz/developers/optimistic-oracle-v3/in-depth-tutorial-insurance.md): Using the Optimistic Oracle V3 to allow for verification of insurance claims.
- [Data Asserter](https://docs.uma.xyz/developers/optimistic-oracle-v3/data-asserter.md): Using the Optimistic Oracle V3 to assert arbitrary off-chain data on-chain.
- [Escalation Managers](https://docs.uma.xyz/developers/optimistic-oracle-v3/escalation-managers.md): Using the full policy escalation manager as an example for modular functionality you could implement with custom escalation managers
- [Sandboxed Oracle Environment](https://docs.uma.xyz/developers/optimistic-oracle-v3/sandboxed-oracle-environment.md): Only required for testing the dispute flow
- [Resolving Testnet Disputes](https://docs.uma.xyz/developers/resolving-disputes.md)
- [Setting Custom Bond and Liveness Parameters](https://docs.uma.xyz/developers/setting-custom-bond-and-liveness-parameters.md): Overview of Setting Customer Bond and Liveness Parameter in UMA's Optimistic Oracle


---

# 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/developers.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.