# KredoPay Docs

## Docs

- [Kredo - An Introduction](https://kredopay.gitbook.io/documentation/kredo-an-introduction.md): The Financial Operating System for Spending Without Custody. Banking Without Accounts.
- [Our Vision](https://kredopay.gitbook.io/documentation/our-vision.md): Kredo’s long-term vision is to redefine banking as an access control system, not a storage system.
- [Market Opportunity](https://kredopay.gitbook.io/documentation/market-opportunity.md)
- [Technology Overview](https://kredopay.gitbook.io/documentation/technology-overview.md): Kredo is built on a combination of cryptographic primitives and minimalist on-chain design.
- [Systems Architecture](https://kredopay.gitbook.io/documentation/systems-architecture.md)
- [Architectural Implications](https://kredopay.gitbook.io/documentation/architectural-implications.md)
- [Kredo Ecosystem](https://kredopay.gitbook.io/documentation/kredo-ecosystem.md): Below is a detailed explanation of Kredo’s key features and how they function together as a unified financial system.
- [$KREDO Token Utility](https://kredopay.gitbook.io/documentation/usdkredo-token-utility.md)
- [Our Revenue Model](https://kredopay.gitbook.io/documentation/our-revenue-model.md)
- [Roadmap Development](https://kredopay.gitbook.io/documentation/roadmap-development.md): Kredo’s roadmap reflects a deliberate progression from core primitives to global financial infrastructure, without introducing user custody or account state at any stage.


---

# 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, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on a page URL with the `ask` query parameter:
```
GET https://kredopay.gitbook.io/documentation/kredo-an-introduction.md?ask=<question>
```
The question should be specific, self-contained, and written in natural language.
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.
