> For the complete documentation index, see [llms.txt](https://lucas-documentation.gitbook.io/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://lucas-documentation.gitbook.io/docs/readme.md).
# Welcome to AutoCap
An automatic DataCap allocator based on On-chain economic activity.
At [CryptoEconLab](https://cryptoeconlab.com/), we've built [**AutoCap**](https://filautocap.xyz/), an automatic DataCap allocator for the [Filecoin Plus (FIL+)](https://fil.org/filecoin-plus) program.
AutoCap enables participants to earn DataCap through a transparent, automated, and activity-based process. Instead of relying on manual applications or discretionary approval, AutoCap distributes DataCap based on **verifiable on-chain economic activity**.
By grounding allocation in observable behavior rather than prior permission, AutoCap introduces a rule-driven mechanism for FIL+ participation, one where DataCap is earned as a consequence of contribution to the network, and allocation outcomes are reproducible, auditable, and proportional by design.
---
# 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://lucas-documentation.gitbook.io/docs/readme.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.
