> For the complete documentation index, see [llms.txt](https://docs.prioticket.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.prioticket.com/getting-started/octo-and-prioticket.md).
# OCTO & Prioticket
Seamless Integration, Maximum Flexibility
At Prioticket, we are proud supporters of **OCTO**, one of the most recognized and widely adopted API standards in the travel industry. In fact, if you’re already an **OCTO-compliant supplier**, connecting to Prioticket is effortless, no additional development required.
We’re also actively working on supporting **OCTO for resellers**, so stay tuned for updates on that front.
***
### Prioticket API or OCTO — Which One Should You Use?
It’s a great question, and the answer is simple: **we believe in flexibility**. Whether you choose to work with **OCTO** or leverage the **Prioticket API**, the choice is entirely yours. Every partner is different, so we leave it up to you to decide what fits your needs best.
To make your decision easier, we’ve created a [detailed comparison](/getting-started/octo-and-prioticket/feature-comparison.md) of the **Prioticket API vs OCTO**, highlighting the key differences, capabilities, and benefits of each option.
---
# 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.prioticket.com/getting-started/octo-and-prioticket.md?ask=&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.
