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

# FAQ

**Q:** When it comes to pricing, what is counted as one transaction?&#x20;

**A:** The transaction is counted at the moment of creation of the exchange mask and EMD for printing (= a single transaction).

&#x20;

**Q:** If the agent only used TCP to check on the fare difference but did not reissue the tickets, is that counted as a transaction?

**A:** No, it is not.

&#x20;

**Q:** If TCP is used for PNR with 3 passengers – is that 1 transaction or 3?

**A:** If the exchange mask is copied, we count 1 transaction for all 3 passengers. If you start a fresh exchange for each passenger, each is counted as one transaction, ie. in this example 3 transactions.

&#x20;

**Q:** Is there any difference between how voluntary and involuntary exchanges are counted?

**A:** No.


---

# 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://cee-systems.gitbook.io/tcp/faq.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.
