> For the complete documentation index, see [llms.txt](https://sendit-markets.gitbook.io/sendit-markets/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://sendit-markets.gitbook.io/sendit-markets/introduction/readme.md). # Introduction to Sendit Welcome to **Sendit**, a new kind of digital marketplace built on blockchain. Think of it as **Amazon or eBay for digital goods** – but with no middleman. Sendit’s mission is to empower creators and buyers by using the blockchain for privacy, security, and fairness. It’s the first decentralized hypermarket for digital products and services, meaning it runs on community rules instead of a single company. That makes it different from traditional platforms: you keep control of your money and data, and the rules are transparent. Sendit offers a unified place for **ebooks, courses, software, NFTs, gaming assets, consulting, and more** – all in one “hypermarket.” Because it’s built on crypto, payments are fast, global, and low-cost, and no personal data is sold. In short, Sendit’s goal is to be a welcoming marketplace where digital creators can sell easily and buyers can trust what they get, all without the headaches of traditional platforms. --- # 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://sendit-markets.gitbook.io/sendit-markets/introduction/readme.md?ask=&goal= ``` `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.