Quote

Immutable USDT → BRL rate snapshot, valid for 5 minutes. Commits nothing and issues no deposit address.

A quote is a price snapshot. It locks the USDT → BRL rate at creation time for 5 minutes. It does not create a conversion, does not issue a deposit address, does not reserve a limit. Quoting is cheap and disposable.

What the quote carries

id: stable quote identifier.
exchange_rate: the snapshotted USDT → BRL rate, considering the fee mode configured for your organization (see Fees model).
source_amount and target_amount: USDT and BRL values implied by the rate.
expires_at: timestamp at which the quote stops being acceptable.

The exact response fields land in the API reference once it is published.

What the quote does not do

Issues no deposit address. The address is born only when you accept the quote. See Accepting the quote.
Reserves no limit. The reserve happens at accept.
Does not lock the end customer. The (user_id, transaction_type) lock is created on the conversion, not on the quote.
Cannot be modified. Quotes are immutable. If the rate changes before accept, create another quote.

5-minute TTL

The short window is deliberate: the offramp integration is programmatic, and the quote captures the rate immediately before accept. If your UX needs more time between obtaining the rate and confirming with the end customer, the right path is to quote again at accept, not to extend the validity.

Don't poll quotes

A quote is disposable. Create one when you need a fresh rate to show the end customer or to accept immediately. Do not loop over quotes, do not store a quote for reuse outside the 5-minute window, and do not treat a quote as a persistent resource.

Prerequisites for quoting

Quote creation needs:

End customer with KYC approved.
End customer's destination Pix key registered.
Amount in USDT (source_amount) or BRL (target_amount).

Without all three, the call fails with a validation error. The error catalog lands in the API reference once published.

Consumed quote

When you accept a quote, it transitions to consumed and gets linked to the conversion created (consumed_by_conversion_id). You cannot accept the same quote twice.

There is one special case: the manual liquidation of a conversion in standby produces a second quote server-side, recorded as consumed and linked to the original conversion via liquidation_quote_id. That quote does not pass through your hand and has no exposed TTL. Details in Standby and manual liquidation.

Next steps

Conversion: where the quote is taken when you accept.
Creating a quote: the call walkthrough.