> For the complete documentation index, see [llms.txt](https://faq.get-protocol.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://faq.get-protocol.io/get-protocol-products/get-protocol-digital-twin.md).

# GET Protocol Digital Twin

## What is the GET Protocol Digital Twin?

GET Protocol's Digital Twin product allows enterprise ticketing companies to twin their existing ticket inventory as NFTs which can then be distributed to attendees as Collectibles. Integrating with the Digital Twin comes with zero operation risk and low effort integration allowing for a hassle free way for ticketing companies to tap into the benefits of NFT & Web3 technology.

Each Collectible can not only be fully customised with event artwork and metadata but can also act as a digital pass into experiences that can be gated exclusively for collectible holders.

You can read more about the Digital Twin on our product page:

{% embed url="<https://www.get-protocol.io/digital-twin>" %}

## How does the Digital Twin work technically?

From a technical perspective, ticketing integrators pass ticket data through an API which mints and distributes an NFT copy to an attendee.

Tickets are currently twinned on the Polygon blockchain and processed through GET Protocol ensuring they are real-time viewable on-chain through our [NFT Ticket Explorer.](https://explorer.get-protocol.io/)


---

# 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://faq.get-protocol.io/get-protocol-products/get-protocol-digital-twin.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.