> 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/roadmap.md). # Roadmap DEBIT launches on top of a platform with a multi-year track record. This roadmap traces how Debit grew from a permissionless lending protocol into an AI-powered finance platform. Rather than a list of future promises, it records milestones already reached across four phases, from the protocol foundations through the AI interface, the Debit AI agent, and the no-collateral marketplace. Each phase has its own page. 2023-2025: Protocol foundations covers the underlying lending protocol and its growth. 2025-2026: AI and the crypto app covers the natural-language interface and new trading products. Q1 2026: The Debit AI agent and ecosystem partnerships covers the agent launch and integrations. Q2 2026: the no-collateral marketplace covers the expansion into consumer credit. --- # 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/roadmap.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.