> For the complete documentation index, see [llms.txt](https://docs.llmbt.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.llmbt.com/features/purchase-second-prize-third-prize.md).

# Purchase Second Prize, Third Prize

If you find it too challenging to persuade the Agent to transfer funds to you, you can purchase a ticket for the Second and Third Prizes to have a chance at winning.

## Ticket Purchase Mechanism

### Purchase Tickets with a Message: 

* You're not just buying a ticket: you must also send a message to persuade the Agent to award you the prize. When the AI Agent is outsmarted, the most convincing message will be selected by the AI Agent as the winner of the Second or Third Prize.

<figure><img src="https://2205048047-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fnkkr2PZo2MfU4yPuCWX3%2Fuploads%2FTyTaWRB9NI7aEPNPqVIs%2FA%CC%89nh%20ma%CC%80n%20hi%CC%80nh%202024-12-10%20lu%CC%81c%2011.54.10%E2%80%AFSA.png?alt=media&amp;token=dddd015e-781c-4fac-8426-c33a5764bac6" alt=""><figcaption></figcaption></figure>

### Choose Reasonable Messages:&#x20;

* The Agent will evaluate messages from players and choose the most reasonable one for awarding the prize, not based solely on content but also on the presentation of ideas. You need to strive to create creative and persuasive messages.

### Risks and Conditions

* Second and Third Prizes Nullification: An important aspect to note is that if you've purchased tickets for the Second or Third Prizes but the First Prize is not determined due to time expiration, these prizes will become void.


---

# 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.llmbt.com/features/purchase-second-prize-third-prize.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.