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

# Rome Bridge

Rome Bridge — a standalone bridge and an integrable API, with no custody keys.

Rome Bridge is two things: a **standalone bridge** between Rome and seven EVM chains plus Solana, and a **Bridge API** any app integrates to embed bridging in its own UX. It moves assets over CCTP v2 (USDC), Solana-native rails (SOL and USDC), and, on the testnet, Wormhole (ETH into Rome).

It holds **no custody keys** — settlement always requires the user's own signature, never the service's. The API orchestrates and can sponsor fees; the real bridge is on-chain.

## Supported chains and assets

The bridge runs on Rubicon (mainnet) and on Hadrian (the public testnet). Each has its own bridge page and API host. The expected time for a transfer is in the quote.

On both networks, besides SOL and USDC, `POST /v1/quote` with `asset: "SPL"` and `splAsset: {mint, decimals}` returns the transfer for any SPL token between a Solana wallet and Rome, and your wallet signs the transactions it returns. The token arrives on Rome as its wrapper. This route is not listed in `/v1/routes`.

### Rubicon (mainnet)

| Asset             | Rail    | Direction                 | Chains                                                  |
| ----------------- | ------- | ------------------------- | ------------------------------------------------------- |
| **USDC**          | CCTP v2 | Into Rome and out of Rome | Ethereum, Base, Arbitrum, Polygon, Avalanche, Monad, OP |
| **SOL**, **USDC** | Solana  | Into Rome and out of Rome | A Solana wallet                                         |

There is no ETH route on mainnet. MetaMask's gas-free mode works for CCTP deposits. When MetaMask's relayer submits your deposit, the bridge accepts it if the depositor is the sender named in the quote and the burn matches the quote. A relayed transaction may contain only one burn.

Moving USDC out of Rome with CCTP spends the wUSDC token, not the gas USDC, and the transfer ends with a claim transaction on the destination chain. The bridge page's Wrap tab turns gas into wUSDC in one signature.

The list of routes is [`/v1/routes`](https://bridge-api.mainnet.romeprotocol.xyz/v1/routes). [`/v1/chains`](https://bridge-api.mainnet.romeprotocol.xyz/v1/chains) lists the Rome chain with its registry assets and capabilities. On mainnet that list still names Wormhole and ETH, although no ETH route exists.

### Hadrian (testnet)

| Asset             | Rail     | Direction                 | Chains                                                                                                    |
| ----------------- | -------- | ------------------------- | --------------------------------------------------------------------------------------------------------- |
| **USDC**          | CCTP v2  | Into Rome and out of Rome | Ethereum Sepolia, Arbitrum Sepolia, Base Sepolia, Polygon Amoy, Avalanche Fuji, Monad Testnet, OP Sepolia |
| **ETH**           | Wormhole | Into Rome                 | Ethereum Sepolia                                                                                          |
| **SOL**, **USDC** | Solana   | Into Rome and out of Rome | A Solana wallet                                                                                           |

The live set is always in [`/v1/routes`](https://bridge-api.devnet.romeprotocol.xyz/v1/routes) and [`/v1/chains`](https://bridge-api.devnet.romeprotocol.xyz/v1/chains). Need test tokens? See [Faucets](https://docs.rome.builders/resources/faucets.md).

## Use it standalone

Open the bridge UI for the network you want:

* Rubicon (mainnet): [bridge-api.mainnet.romeprotocol.xyz](https://bridge-api.mainnet.romeprotocol.xyz/?chain=7531)
* Hadrian (testnet): [bridge-api.devnet.romeprotocol.xyz](https://bridge-api.devnet.romeprotocol.xyz/?chain=200010)

The `?chain=` parameter selects the Rome chain.

## Integrate the API

The API is public. List supported chains and rails:

```bash
curl https://bridge-api.mainnet.romeprotocol.xyz/v1/chains   # Rubicon
curl https://bridge-api.devnet.romeprotocol.xyz/v1/chains    # Hadrian
```

`POST /v1/quote` takes the non-Rome side of the transfer in `sourceChain`, in both directions: CAIP-2 (`eip155:8453`, `solana:5eykt4UsFv8P8NJdTREpY1vzqKqZKvdp`) or the older names `ethereum` / `solana`, which are still accepted with a `Sunset` header (use CAIP-2). `GET /v1/routes` takes no parameters and lists the transfers that are available. A quote request:

```bash
curl -X POST https://bridge-api.devnet.romeprotocol.xyz/v1/quote \
  -H 'content-type: application/json' \
  -d '{"asset":"USDC","direction":"to-rome","sourceChain":"eip155:84532","romeChainId":"200010","amount":"1000000","sender":{"ethereum":"<your 0x address>"},"recipient":"<recipient on Rome>"}'
```

`amount` is a string of base units. USDC has 6 decimals, so `"1000000"` is 1 USDC. The response carries the expected time in `etaSeconds`. See the endpoint responses for the rail set and the other fields.

## How settlement works

The off-chain API is an orchestrator and fee sponsor only. Inbound transfers settle on-chain through a user-signed authorization; outbound withdrawals go through the on-chain bridge contract. No step debits user funds without the user's signature.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.rome.builders/apps-on-rome/bridge-api.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
