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

# Why Spider is Best?

Spider isn't just building an AI platform, it's constructing the infrastructure for a revolutionary future. Here's what sets Spider apart:

**A Scalable, Secure, and User-Friendly Ecosystem:**

We're building a decentralized ecosystem designed for growth and accessibility. This means robust infrastructure that can handle the demands of a thriving AI community, coupled with robust security measures to ensure user trust. And let's not forget – user-friendliness is paramount. We're committed to creating a platform that's intuitive and welcoming for everyone.

**Empowering Developers, Seamless User Experience:**

At the heart of Spider lies a comprehensive suite of features designed with two key goals in mind: empowering developers and creating a seamless user experience. Here's how:

* **Privacy-Focused Chrome Extension:** Our Chrome extension is the cornerstone of data collection. It's built with privacy in mind, allowing users to safely contribute data while offering complete control. You can enable or disable data harvesting at any time, fostering transparency and trust. Additionally, the community can collectively blacklist unwanted websites, with decisions made through a Decentralized Autonomous Organization (DAO), ensuring community control.
* **Multiple Extensions, One Secret:** Power users rejoice! You can manage multiple extensions with a single secret key, streamlining your workflow within the Spider ecosystem.
* **Spidey Sense (Coming Soon):** Introducing a revolutionary personal AI model under development by the Spider team. This AI companion learns, adapts, and grows alongside you. (Note: Spidey Sense will be available through a subscription-based model using $WEB tokens.)
* **Multilingual AI Model Training:** We understand the struggles of AI startups and enterprises – a lack of multilingual datasets. Spider breaks down this barrier. Our platform allows developers to create AI models proficient in specific languages, leveraging the vast knowledge base of global content.

**Global Orderbook Protocol for Streamlined Data Sharing:**

Unlike other DApp scaling solutions, Spider boasts a game-changing feature – a shared global orderbook. Here's how it elevates data sharing:

* **Enhanced Liquidity and Price Discovery:** This unique feature allows orders placed on one marketplace to be fulfilled on another. Imagine increased liquidity, more efficient price discovery, and a more robust overall market for data.
* **Transparent and Rewarding for the Community:** Our global orderbook protocol fosters transparency in dataset sharing, ensuring fair rewards for the community that contributes valuable data to the network.


---

# 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://spider-2.gitbook.io/the-spider-whitepaper/the-spider/why-spider-is-best.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.