> For the complete documentation index, see [llms.txt](https://learn.onopen.xyz/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://learn.onopen.xyz/the-open-ticketing-ecosystem/explorer.md).

# OPEN Ticket Explorer

<figure><img src="/files/hMXaohEMMx4BOntKVCaC" alt=""><figcaption></figcaption></figure>

The beauty of onchain ticketing data is the transparency and accountability it affords in allowing anyone around the world to see real-time tickets being issued. We do this through our Sub Graph in collaboration with The Graph - which powers our Ticket Explorer.

On the Ticket Explorer you can see top level statistics on the amount of onchain tickets issued through OPEN on a year, month and weekly basis.

Below you can see individual tickets being sold by OPEN ticketing integrators along with the various states that these tickets go through, such as being sold, re-sold, scanned and invalidated.

You can visit the explorer on [explore.onopen.xyz](https://explore.onopen.xyz/)


---

# 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://learn.onopen.xyz/the-open-ticketing-ecosystem/explorer.md?ask=<question>&goal=<endgoal>
```

`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.
