> 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/the-platform-and-business-model/the-debit-ai-agent.md).

# The Debit AI agent

Debit is a natural-language interface for onchain finance. A user describes an intent, and the agent constructs the steps: cross-chain swaps, bridging, transfers, borrowing, depositing, staking, claiming rewards, and loan repayment. It auto-builds approvals, handles network switching, and displays transaction details before anything is signed. Connecting a wallet takes a single signature with no gas, and the agent is currently in beta.

This is where DEBIT is consumed. Access to the agent is metered in DEBIT, where the token is used as a native protocol fee for the agent, and a user tops up a DEBIT balance to keep using it.


---

# 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/the-platform-and-business-model/the-debit-ai-agent.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.