> For the complete documentation index, see [llms.txt](https://kredopay.gitbook.io/documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://kredopay.gitbook.io/documentation/our-vision.md).

# Our Vision

Kredo’s long-term vision is to redefine banking as an **access control system**, not a storage system.

Rather than asking *“How much money do you have?”*, Kredo asks:

* *What are you allowed to do?*
* *Under what conditions?*
* *For how long?*
* *With what limits?*

In this model:

* Financial access is programmable
* Identity can be proven without exposure
* Liquidity is shared, not owned
* Users are never custodians of pooled capital

Kredo envisions a future where:

* Banking works without accounts
* Financial inclusion does not require custody
* Privacy is structural, not optional
* On-chain systems scale without per-user state growth
* Machines, agents, and humans interact financially under the same authorization framework

This vision positions Kredo not merely as a product, but as **financial infrastructure** for a post-account economy.


---

# 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://kredopay.gitbook.io/documentation/our-vision.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.