> For the complete documentation index, see [llms.txt](https://debit.teller.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://debit.teller.org/how-debit-works/how-no-collateral-pre-qualification-works.md).

# How no-collateral pre-qualification works

No-collateral borrowing works differently, because the loan itself is made by a third-party licensed lender rather than by the protocol. A borrower answers a short set of questions, through the agent or the pre-qualification form: where they live, how much they want to borrow, their income, and a rough credit tier. Debit checks those answers, together with signals from a connected wallet, against the eligibility rules for no-collateral products, and returns whether the borrower pre-qualifies and which offers to explore across personal loans, credit cards, business loans, HELOCs, and auto refinancing. The check is soft: it uses no hard credit pull and posts no collateral. Pre-qualification is a preview rather than an approval, and final terms are set by the lender that ultimately underwrites the loan.


---

# 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://debit.teller.org/how-debit-works/how-no-collateral-pre-qualification-works.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.
