A base-quantity market buy requests a number of asset units; a quote-quantity market buy expresses how much of the payment asset to spend. For ALP/USDT, that means buying a stated amount of ALP versus spending a stated amount of USDT. The execution price connects the two, so a fixed spend does not fix acquired units, and fixed units do not fix spend. Fees and venue rules add separate constraints.
The practical question is which quantity your plan authorizes. “Buy ten units” and “spend 1,000 USDT” can coincide in a preview and diverge when the order reaches the market. The following worksheet shows that divergence using an invented spot pair, then turns the result into a reconciliation record.
Choose the unit before choosing the parameter
In ALP/USDT, ALP is the base asset and USDT is the quote asset. A displayed price of 100 USDT per ALP is a conversion rate, not a promise that every unit will trade there.
| Your instruction | Quantity being specified | Quantity determined through execution |
|---|---|---|
| Buy 10 ALP | Base units requested | Gross USDT paid |
| Spend 1,000 USDT buying ALP | Quote amount requested | Gross ALP acquired |
Neither row specifies both a guaranteed final quantity and a guaranteed final cost. A market instruction also does not establish that the entire request will fill. The market-versus-limit guide explains the separate choice between immediate execution and an explicit price boundary.
Binance Spot's standard new-order endpoint distinguishes quantity, expressed in the base asset, from quoteOrderQty, expressed in the quote asset. For a market buy, the latter asks to buy as much base asset as the quote amount can purchase. Its documentation says the executed notional is made as close as possible to that amount while respecting lot-size rules. Binance Spot new-order specification.
Bybit V5 uses qty with marketUnit for spot market orders. Its documented spot market-buy default is value-based; baseCoin and quoteCoin explicitly select the unit. The same page says perpetual, futures and option orders use quantity. Bybit V5 order parameters.
These examples describe those API paths, not a universal meaning for a field called “amount.” A connector or application can translate its own input before submission. Record both the user's intended unit and the actual exchange request.
Two alternatives against the same frozen book
Assume the fictional ALP/USDT market has these asks:
| Ask price, USDT per ALP | ALP available at this level |
|---|---|
| 100 | 4 |
| 102 | 20 |
Compare two alternative purchases against this same starting book. They are not consecutive orders. Assume the offers remain available, all modeled quantities are valid, no other trader intervenes, fees are excluded and the orders complete as modeled.
A ten-ALP request consumes four ALP at 100 and six at 102. Its gross cost is 4 × 100 + 6 × 102 = 1,012 USDT.
A 1,000-USDT request consumes the same first four ALP for 400 USDT. The remaining 600 USDT buys 600 ÷ 102 = 5.88235294 ALP, approximately. Total acquired quantity is approximately 4 + 5.88235294 = 9.88235294 ALP.
| Alternative instruction | Gross ALP filled | Gross USDT paid | Average price, USDT per ALP |
|---|---|---|---|
| Buy 10 ALP | 10 | 1,012 | 101.20 |
| Spend 1,000 USDT | About 9.88235294 | 1,000 | About 101.190476 |
At the first ask, 1,000 USDT appeared equivalent to ten ALP. Across the modeled book, the base-sized purchase costs 12 USDT more, while the quote-sized purchase receives about 0.11764706 fewer ALP.
The small difference between average prices comes from how much of the second level each alternative consumes. It does not demonstrate a better trading strategy. Both calculations depend on a frozen book that can change before execution; the order-book depth worksheet develops that uncertainty.
Converting a budget into base units changes the instruction
Suppose an interface accepts a 1,000-USDT budget but its integration submits only base quantity. Dividing by a reference price of 100 produces ten ALP. That translation has created a base-sized market request. The original budget is no longer enforced merely because it appeared in the interface.
In the worksheet, that request needs 1,012 USDT before fees. With insufficient available funds, the outcome depends on the venue's rules; do not assume it will politely resize itself to the intended budget.
An estimate using a more conservative price can leave room, but it still needs an explicit policy for price movement, fees, completion and any remainder. When the plan requires a price boundary, select a supported instruction that expresses it and accept the possibility of nonexecution. A cached ticker divided into a cash balance does not establish a binding execution limit.
If the reference comes from an oracle rather than an executable ask, check its update policy and age separately. The oracle staleness and deviation guide explains why an observed reference can lag current trading conditions. Even a current reference does not reveal all available asks.
Keep gross spend separate from all-in cash usage
A quote-sized buy does not by itself answer which asset pays commission. In a separate hypothetical accounting case, 1,000 USDT of gross execution plus a 1-USDT fee requires 1,001 USDT. If a different fee rule deducts base units instead, gross acquired quantity and net credited inventory differ.
These are alternative assumptions, not claimed fee policies for either venue above. Read the fee-currency guide before deciding what balance to reserve. Do not count a base-asset commission as an additional quote debit as well.
Quantity increments and minimums can also leave a remainder or make a proposed request invalid. Apply the decimal-precision procedure and order-minimum checks after identifying the unit. Accurate decimal handling cannot correct a value submitted in the wrong asset.
Reconcile what was bought, not what the preview predicted
Use this record for each purchase:
| Record field | Question it answers |
|---|---|
| Intended amount and asset | Was the plan for ten ALP or 1,000 USDT? |
| Market, side and actual sizing parameter | What did this endpoint receive? |
| Distinct fills: base quantity and quote value | What actually exchanged hands? |
| Commission amount and asset | What changed beyond gross execution? |
| Terminal status and unresolved remainder | Has the instruction finished? |
| Available balance after reconciliation | What can the next action use? |
Sum confirmed gross quote value and divide by confirmed gross base quantity to calculate average execution price. When filled base quantity is zero, leave that average undefined; zero is not a free execution. Binance's user-data stream documentation likewise describes calculating average price from cumulative quote and base fills.
One order can contain multiple executions. Bybit's trade-history reference exposes execution quantity, value, identity and fee currency for that accounting. Use the partial-fill management guide when the request finishes short or its status remains unresolved. An acknowledgement alone cannot populate the completed worksheet.
This spot conversion also differs from valuing or settling a derivatives position. Contract units, collateral and settlement cash flows need their own definitions; the futures settlement versus mark-to-market guide follows that separate ledger.
Before reusing a fill quantity for an exit or another automated step, compare it with fees, reservations and current account state. The defensible result is an observed gross purchase and net available inventory, with the original sizing intention preserved beside them.
Editorial method: Prepared with AI assistance from primary exchange documentation reviewed on 23 October 2026. The original frozen-book worksheet is hypothetical and was checked arithmetically. It does not establish KLINEO support for either sizing parameter or predict an execution outcome.