> For the complete documentation index, see [llms.txt](https://docs.rozo.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.rozo.ai/integration/api-doc/bridge-api.md).

# Bridge & Wallet API

Use this API when **you provide the destination address on every request** — bridging your own funds, topping up a wallet, or paying an arbitrary on-chain address.

Every payment request includes a `destination.receiverAddress`, and ROZO routes the funds cross-chain to it.

## Pages

* [API Quick Start](/integration/api-doc/bridge-api/api-quick-start.md) — bridge 1 USDC from Base to Stellar in one call.
* [Wallet Top-up](/integration/api-doc/bridge-api/wallet-topup.md) — `anyAmount` deposits: send any amount, the system detects it automatically.
* [Get Fees](/integration/api-doc/bridge-api/get-fees.md) — preview fees with `dryrun=true` before creating a payment.
* [Stellar Smart Account Payments](/integration/api-doc/bridge-api/stellar-contract-payments.md) — pay from Soroban contract addresses (C-addresses) to EVM and Solana.

## Webhooks

Bridge and wallet apps get the same [Webhook](/integration/api-doc/merchant-api/webhook.md) notifications (`payment_payin_completed`, `payment_payout_completed`) as merchants — register your app on [partners.rozo.ai](https://partners.rozo.ai) (you'll get a `wallet_<slug>` appId) and configure your webhook URL there. Without a registered appId, poll the payment status instead.

## Looking to accept payments instead?

If you are a merchant with a **preconfigured receiving wallet** (no destination address needed per request), use the [Merchant API](/integration/api-doc/merchant-api.md).


---

# 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://docs.rozo.ai/integration/api-doc/bridge-api.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.