> For the complete documentation index, see [llms.txt](https://docs.teller.org/teller-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.teller.org/teller-docs/protocol-1/overview.md). # Overview Teller’s unique cloud-based infrastructure can connect to, and privately compute credit and banking data to generate individual loan terms based on a users’ creditworthiness. This allows depositors to earn a passive income, while borrowers are able to request both secured (over-collateralized) and unsecured (under-collateralized) loans. At the heart of the Teller Protocol are the main contracts that make Teller tick. We are highlighting the main methods of these contracts in the following documents. You can also get started by joining the #developers channel on our [community Discord](https://discord.com/invite/Ujnvh8d) or by visiting our[ Github for the complete source code](https://github.com/teller-protocol/teller-protocol-v1). --- # 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.teller.org/teller-docs/protocol-1/overview.md?ask=&goal= ``` `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.