# Welcome to ROZO

Our story begins in the summer of 2025, in a small boba shop in San Francisco that accepted USDC.

I scanned their QR code with my mobile USDC wallet, but my app showed error.

<figure><img src="https://2103448998-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FhuTMWMzO32xbGDjNWeOa%2Fuploads%2Fgit-blob-afc7b1b1ba26844c8690b2a20841408e7aa3cd13%2FScreenshot%202025-11-29%20at%205.27.36%E2%80%AFPM.png?alt=media" alt="" width="173"><figcaption></figcaption></figure>

It turned out the merchant only accept USDC on Base chain, while my wallets only support USDC on Stellar. USDC on Stellar is not the same as USDC on Base.

<figure><img src="https://2103448998-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FhuTMWMzO32xbGDjNWeOa%2Fuploads%2Fgit-blob-4e58941c8b4667851bcc4ba1b310ac54623d0e61%2FScreenshot%202025-11-29%20at%205.27.39%E2%80%AFPM.png?alt=media" alt="" width="375"><figcaption></figcaption></figure>

Stablecoins are the best form of money on the Internet, but the user experience is still stuck in the early days. USDC exists on 29 different blockchains — and that’s not even counting USDT.

To pay for a coffee, why do we need to understand 29 chains, different stablecoins, different bridges, different fees? That’s *not* how money should work.<br>

We’re building ROZO, the Visa for Stablecoins. We hide the complexity, and we are building the stablecoin abstrations. You only need to think in *intents.*

> “I want to pay $3.25 for boba with 10% tips.”
>
> “I want to buy $100 BTC.”
>
> “I want to earn 10% APY with a pool with $10M+ TVL.”

Welcome to ROZO.

Let's hide the wires and use a new way of transacting.


---

# Agent Instructions: 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:

```
GET https://docs.rozo.ai/start/readme.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.