> 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/developers/introduction.md).

# Introduction

This section gives developers what they need to evaluate the Credit Coop contracts — as a Borrower, a Lender, a Vault Curator, or an integrating protocol — and to build against them.

The current live protocol is **v2** (Line-Of-Credit-v2 and the Vaults contracts). Its architecture is documented in [Protocol Architecture (v2)](/developers/architecture-v2.md). The original v1 material is preserved under [V1 Developer Material (Archived)](/developers/v1-developer-material.md) for teams still interacting with legacy deployments.

The codebase is available on our [GitHub](https://github.com/credit-cooperative). Platform data — facilities, vaults, positions, benchmarks — is available through the [Credit Coop Platform v3 API](/platform-api/credit-coop-platform-v3-api.md).

Credit Coop's contracts are deployed on several networks, including Ethereum, Base, Arbitrum, and Solana (originations). For contract addresses see [Deployed Contracts](/developers/deployed-contracts.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 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.creditcoop.xyz/developers/introduction.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.