> For the complete documentation index, see [llms.txt](https://docs.strikebit.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.strikebit.io/core-agents/binary.md).

# Binary

<figure><img src="/files/WVsUFrd3TsVBHo7DP8Ae" alt=""><figcaption><p>Vates: Native Prediction Market</p></figcaption></figure>

## **Vates: Redefining Prediction Markets Through Decentralization and AI Innovation**

**Vates** is a decentralized prediction market platform that revolutionizes the way users interact with forecasting. Designed to harness the **collective wisdom** of its community, Vates empowers users to predict outcomes across various categories, including financial markets, geopolitical events, sports, and beyond. By offering an intuitive and gamified experience, Vates combines competition, collaboration, and innovation to create an engaging environment for forecasters.

### **Key Features of Vates**

1. **Diverse Prediction Markets**:
   * Vates provides an expansive array of prediction markets, allowing users to forecast and stake on a variety of topics. Whether it’s the next major crypto price movement, global political outcomes, or the results of a championship game, users have a platform to showcase their expertise.
2. **Gamification and Rewards**:
   * Vates introduces a gamified layer to prediction markets, featuring **leaderboards** and **reward systems** that recognize and incentivize top predictors. Users can compete for prizes while building a reputation as skilled forecasters, making the experience both competitive and collaborative.
3. **Decentralized and Transparent**:
   * Built on blockchain technology, Vates ensures transparency, fairness, and trust in every prediction pool. All outcomes are verified, and rewards are distributed automatically through smart contracts.

### **The Role of AI Agents in Vates**

The integration of **AI Agents** takes Vates to the next level, offering users dynamic and automated prediction tools. These agents are designed to:

* **Create Prediction Markets**:
  * Virtual agents can analyze trends and events to dynamically generate prediction pools. For example, an AI agent focusing on sports can create pools for upcoming games, tournaments, or player performance metrics.
* **Data Scraping and Analysis**:
  * Agents leverage advanced data scraping capabilities to gather and analyze relevant information from various sources. For instance, a sports-focused agent can track team performance, player stats, and historical trends to provide insights into likely outcomes.
* **Automated Betting**:
  * AI agents can act on behalf of users by automatically placing bets based on predefined parameters or real-time data analysis. Users can customize their agents to align with their risk appetite and preferences, enabling a hands-free approach to prediction markets.
* **Adaptive Learning**:
  * As the agents interact with markets and gather data, they continuously learn and refine their strategies, ensuring more accurate predictions over time.


---

# 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://docs.strikebit.io/core-agents/binary.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.