Tempo Routes is an API from Tempo, the payments-focused Layer 1 blockchain, that lets a business move stablecoins between Tempo and other networks through a single integration. Tempo describes it as a way to connect stablecoins, currencies, networks, and bank accounts in one interface (Tempo Routes). The developer documentation states that Routes is in beta and that access is arranged by contacting Tempo (Tempo Docs, Routes).
This article explains how a route is defined, which networks and tokens appear in Tempo's live route directory, how quotes and fees work, how deposit addresses and transfers differ, and how FX routes swap one currency for another on Tempo. For background on the chain itself, see What is Tempo blockchain.
What is Tempo Routes?
Tempo Routes is a set of API endpoints that move stablecoins from a source network and token to a destination network and token. Routes prepares the funding instructions or source-chain calls, then tracks delivery to the recipient. A route starts with a successful source transaction, and the application confirms completion at the destination.
That definition comes from the "How Routes works" section of Tempo's documentation, which also says that payments staying on Tempo should use Tempo's send-payment or stablecoin swap guides instead, while Routes itself handles cross-currency swaps on Tempo through FX routes (Tempo Docs, How Routes works). The marketing page groups the product around three ideas: reaching customers in the currencies they use, converting between supported stablecoins at a fixed 1:1 rate, and connecting once to a set of liquidity providers, stablecoin issuers, and bank rails (Tempo Routes).
Routes does not sign transactions. The API key authenticates the application, and a wallet or the business's own signer submits source transactions (Tempo Docs, Set up Routes).
Which networks and stablecoins does Tempo Routes support?
Tempo's FAQ names Ethereum, Base, Polygon, BNB Smart Chain, Solana, Tron, and Tempo as networks for moving supported stablecoins, and asks businesses to confirm the specific routes they need with Tempo (Tempo Routes, FAQ). The live route directory in the docs lists more source networks than that summary.
The "Supported routes" page shows source assets on Ethereum, Optimism, Polygon, Monad, Arbitrum, Avalanche, Arc, BNB Smart Chain, Base, HyperEVM, Solana, Stellar, and Tron, each paired with a destination token on Tempo (Tempo Docs, Supported routes). Destination tokens on Tempo include OUSD, pathUSD, USDC.e, and USDT0. The directory also lists outbound routes from Tempo to other networks, plus testnet routes on Tempo Testnet (Tempo Docs, Supported routes).
Tempo notes that an organization's access policy can narrow the routes its API key can use, and advises matching tokens by network and contract address rather than by symbol alone (Tempo Docs, Supported routes). For more on pathUSD's role on the chain, see What is pathUSD.
The table below samples rows from the live directory as published on Tempo's docs. It is not the full list.
Source | Destination | Funding methods | Fee coverage |
|---|---|---|---|
USDC on Ethereum | OUSD on Tempo | Transfer, deposit address | Available |
USDT on Tron | OUSD on Tempo | Transfer, deposit address | Available |
USDC on Solana | USDC.e on Tempo | Transfer, deposit address | Available |
USDC on Arbitrum | USDT0 on Tempo | Deposit address | Available |
OUSD on Tempo | USDC on Base | Transfer, deposit address | Available |
OUSD on Tempo | USDT on Tron | Transfer, deposit address | Not available |
EURC.e on Tempo | OUSD on Tempo | Transfer | Not available |
Source for every row: Tempo Docs, Supported routes. The directory is also readable by API at GET /v1/routes, with filters for source and destination chain and token; requests without a key use the public rate limit, and a key with the data:read scope returns the routes available to that organization (Tempo Docs, Read the route directory).
How does the Tempo Routes API work?
An integration follows six steps in Tempo's docs: try a route in the browser demo, set up an API key, pick a pair and funding method, request a quote, build a deposit or transfer flow, and track delivery to completion or refund before crediting a balance (Tempo Docs, Build a Routes integration).
API keys are created in Tempo Console and carry three scopes (Tempo Docs, Set up Routes):
routes:read for quotes and status reads on transfers and deposits.
routes:write for creating transfers and deposit addresses and registering source transactions.
data:read for reading the route directory under the organization's access policy.
Requests go to api.tempo.xyz with a tempo-api-key header. Create requests require an idempotency-key header, and Tempo says matching requests with unchanged inputs replay the successful response for 24 hours, while a request with changed inputs conflicts (Tempo Docs, Set up Routes).
How do quotes and fees work on Tempo Routes?
Every flow starts with a quote. Deposit flows call GET /v1/routes/deposit-addresses/quote and transfer flows call GET /v1/routes/transfers/quote, both with routes:read (Tempo Docs, Quotes and fees). A quote prices the route but does not create or reserve a transfer.
For transfers, the mode parameter fixes one side: exactSource fixes how much is sent, and exactDestination fixes how much the recipient receives. The returned destinationAmount already includes route deductions, and the fees array lists only separately charged fees, so an empty array can still come with deductions. When a quote returns quote.expiresAt and that time passes, the application requests a new quote (Tempo Docs, Quotes and fees).
Organizations approved for subsidies can send subsidize: true on the quote and create request. Tempo then guarantees normalized 1:1 delivery, meaning the recipient receives the amount sent; for transfers this applies to exactSource only, and requests without approval are rejected with a routes_subsidy_* error code (Tempo Docs, Offer 1:1 delivery). Tempo's product page asks businesses to contact the company for pricing (Tempo Routes).
How do deposit addresses work on Tempo Routes?
A deposit address is a reusable Routes address on another network, such as Ethereum or Tron, that a customer can fund from any external wallet. Each address accepts the networks and tokens of its route and delivers funds to the Tempo recipient the business chose (Tempo Docs, Accept deposits).
To create one, the business needs a backend API key, a route with deposit-address support, a Tempo recipient, and a refund address on the source network. The create call is POST /v2/routes/deposit-addresses, with refund addresses keyed by chain family such as evm. Refunded deposits move from refunding to refunded (Tempo Docs, Accept deposits). Tempo notes that quotes on some routes, including those from Ethereum, Polygon, BNB Smart Chain, and Tron, return a quote_not_available error unless the recipient and refund address are supplied (Tempo Docs, Quote the deposit).
The product page says deposited funds can land in a Tempo account, a private Tempo Zone, or a Tempo Earn vault (Tempo Routes). The developer docs are more specific: depositing into Earn or a Zone is a separate operation after delivery, and direct Routes transfers into vaults or Zones are not implemented, with those endpoints returning HTTP 501 (Tempo Docs, Track delivery).
What is the difference between a deposit and a transfer?
The choice depends on who submits the source transaction. With a deposit address, the sender pays from any external wallet to an address shown to them. With a transfer, the business's application signs the source calls through a connected wallet or its own signer (Tempo Docs, Choose a flow).
A transfer is created with POST /v1/routes/transfers and returns an id beginning with rtr_ and an action object containing the unsigned source-chain calls. Tempo notes that only the create response includes action; later reads do not return it (Tempo Docs, Make a transfer). Delivery is tracked with GET /v1/routes/transfers/{id} for transfers and GET /v1/routes/deposits for deposits. Transfer states include awaiting-source, processing, completed, expired, refunding, and refunded; deposit states include detected, bridging, and settling (Tempo Docs, Delivery states).
On timing, Tempo's FAQ says transfer times vary by network and route and asks businesses to review expected times with Tempo (Tempo Routes, FAQ).
Can Tempo Routes convert between currencies?
Yes. Routes connects to Tempo FX, where third-party market makers quote supported currency pairs against live foreign exchange benchmarks. Tempo says dollar to euro conversion is live through a pool that pairs EURC.e with OUSD, and that a single transaction can convert and pay a recipient's wallet at any hour, settling onchain in under a second (Tempo Routes, FAQ).
In the docs, an FX route is a route with both ends on Tempo and a different currency on each end, such as OUSD to EURC.e. It differs from other routes in four ways (Tempo Docs, Swap currencies):
Only accounts on the organization's account list can swap; a quote for an unlisted sender returns 404.
The sender and recipient are the same account.
A quote expires within seconds, and the swap call reverts after that expiry.
The price is built into the quoted amounts, and the route adds no separate fee.
Account lists are tied to the pool contract that fills the swaps. Every pool has a default list with sponsor ID 0 managed by the pool owner, and organizations can have their own lists, which Tempo sets when it enables access (Tempo Docs, Account lists on FX routes).
Frequently asked questions
These answers restate points from Tempo's Routes product page and developer documentation.
Is Tempo Routes generally available?
No. Tempo's documentation labels Routes as beta and directs teams to contact Tempo for access (Tempo Docs, Routes).
Can I try Tempo Routes without an API key?
Yes, in part. Tempo's browser demo quotes listed routes without a key and previews 1:1 delivery where a route supports it (Tempo Docs, Build a Routes integration).
Can I use my existing wallet provider?
Yes. Tempo says businesses can use the wallet infrastructure they already support to sign and broadcast transactions (Tempo Routes, FAQ).
Does Routes handle bank payouts?
The docs point bank funding and payouts to Tempo's payments and ramps partner page rather than the Routes endpoints (Tempo Docs, Use funds after delivery). For network details such as chain ID and RPC, see Tempo mainnet launch date, chain ID and RPC, and for token and fee questions see Does Tempo have a token.

