Xebra
Move native USDC between chains over Circle CCTP, from your own app.
Xebra moves native USDC between Stellar, Sui, Solana and EVM chains over Circle's Cross-Chain Transfer Protocol (CCTP). USDC is burned on one chain and minted on the other. Nothing is wrapped, and no pool sits in the middle.
You can build it into a wallet, an exchange or any app that holds USDC:
- Quote a transfer: what it costs and what the recipient gets.
- Build it: the API returns unsigned transactions, in the order the wallet signs them.
- Track it: from the burn to the mint on the destination.
- Claim it, in the rare case a delivery does not complete on its own.
Xebra never holds keys or funds. The API builds transactions; your user's wallet signs and sends them. No endpoint takes a private key.
Quickstart
A first quote and a first unsigned transfer, in five minutes.
API reference
Six endpoints over HTTPS, described in OpenAPI 3.1, with a playground.
SDK
@xebra/sdk for TypeScript: a typed client, and builders for your own RPC.
How a transfer goes
quote ──► build ──► user signs and sends ──► burn on source ──► Circle attests ──► mint on destination- Ask for a quote with
GET /v1/quote, and show the user the fees and what arrives. - Build with
POST /v1/transfers. You get one or more steps, each an unsigned transaction. - The user's wallet signs each step in order, and you send it to its chain.
- Circle attests the burn. Circle's Forwarding Service, or Xebra's forwarder on Stellar, mints on the destination. See who delivers.
- Follow it with
GET /v1/transfers/{chain}/{tx}until it isdelivered.
Where to go next
- New to CCTP? Read how CCTP works and fees.
- Sending from a particular chain? Start with the guides.
- Using Claude or another AI assistant? Connect the MCP server.
- Every page on this site is also available as Markdown: add
.mdto its URL, or read/llms.txt. - Want to see it work first? Every mainnet transfer we have made links to its transactions on both chains.
Talk to us
Integrating Xebra into a wallet, exchange or app? Write to partners@xebra.exchange or message @xebra_exchange on X.