> For the complete documentation index, see [llms.txt](https://docs.playai.network/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.playai.network/playstudio/madrims/data-usage-and-integration.md).

# Data Usage and Integration

### Madrims Data Usage & Integration

* **Decentralized Vision Data Pipeline:** Madrims smart glasses capture real-time vision data from users in the physical world, streaming it directly into the PlayAI and Hub.xyz combined pipeline. This partnership turns raw footage from Madrims into verified, structured datasets ready for enterprise use across AI, robotics, and finance.
* **Play Collective Integration:** All data collected by Madrims is funneled into Play Collective - PlayAI’s collaborative data aggregation and incentivization layer. Here, the data is annotated, labeled, and quality-checked within Hub.xyz’s end-to-end infrastructure. Contributors are rewarded for data that helps improve agent intelligence and application workflows, fueling the development of smarter agents and more robust decentralized AI services.
* **Enterprise and Agent Workflows:** Quality-controlled Madrims datasets are delivered as live, AI-ready streams for training models in robotics, trading algorithms, real-time market analytics, and situational awareness. As PlayAI agent workflows are directly connected to Hub’s low-latency pipelines, agents can react to live signals, like emerging trends or threats, based on this vision data, making PlayAI a bridge between physical environments and next-generation machine intelligence.

This initiative represents a move toward “decentralized living,” where privacy, portability, and verifiable digital agency are foundational, and where users, developers, and enterprises all benefit from frictionless, high-quality, and incentivized real-world data.


---

# 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.playai.network/playstudio/madrims/data-usage-and-integration.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.
