> For the complete documentation index, see [llms.txt](https://docs.creditcoop.xyz/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.creditcoop.xyz/user-documentation/v1.md).
# User Documentation (v1)
User Documentation mentioned here is all available at our [User Doc Site](https://creditcoop.notion.site/Credit-Coop-User-Documentation-68141d78ffa54a38b4609b42c64bb93c?pvs=4).
App FAQ
The App FAQ is available as part of our dedicated User Documentation site.
Questions are grouped by stages in the loan life cycle. [Click to discover it!](https://www.notion.so/creditcoop/0755372b767f463cb01e0cf41aeb55e2?v=be40f404e6924029bfdd11f478cc3a31\&pvs=4)
User Journey Guide
A step-by-step guide through the journey of Line deployment (done by the Servicer), borrowing and lending, repayment and what happens if things don't quite go to plan.
The User Journey Guide is available as part of our dedicated User Documentation site. [Click to discover it](https://www.notion.so/creditcoop/28f3e4d84a134ea78f6aa0f501686dd7?v=d2459cb84afa40228ff573088a1d0478\&pvs=4)!
Glossary
For App users, the Glossary explains terms used on the front-end and is available as part of our dedicated User Documentation site. [Click to discover it!](https://www.notion.so/creditcoop/b9f570048e2841c59c029f3e14469d42?v=45a10c249fc94cbab57ad72bb28c8168\&pvs=4)
*Developers and Integrators accessing the underlying smart contracts directly should also refer to the* [*archived v1 developer docs*](/developers/v1-developer-material.md)*.*
---
# 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.creditcoop.xyz/user-documentation/v1.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.