> For the complete documentation index, see [llms.txt](https://docs.flock.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.flock.io/flock-products/ai-marketplace/deep-dive/function-breakdown.md).
# Function breakdown
This system streamlines the process of creating, deploying, and utilising customised AI models.
### Function breakdown
AI Marketplace operates through various phases, incorporating model proposals and live chatting.
**Core components and workflow:**
1. **Model Proposal:**
Submit AI model proposals, describing tasks and required data sources for applications like AI x Web 3 projects or longevity research.
2. **Data Contribution:**
To encourage the submission of high-quality data, we offer rewards of tokens.
3. **Voting on Knowledge Base:**
Voting system for community members to validate the contributed knowledge, ensuring relevance and safeguarding against malicious content.
4. **Chatbot Deployment:**
Top-rated models are deployed as interactive bots on Discord channels, broadening the accessibility of AI to a wider audience.
5. **Reward System:**
Model Proposers, Data Contributors and Model Hosts receive rewards based on data relevance, bot usage, and user feedback.
---
# 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.flock.io/flock-products/ai-marketplace/deep-dive/function-breakdown.md?ask=&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.