The three quote shapes

POST /v1/trades/quote answers { "quote": { ... } }. The object has one of three shapes, because the venues differ. They are told apart by two flags, not by a kind field.

A pool quote has no expectedOut. A client that reads the curve's field names off a pool quote shows "you receive 0" beside a good quote. Branch on the flags first.

type AnyQuote = Record<string, any>;

function receive(q: AnyQuote): { out: string; min: string } {
  if (q.collectible === true) return { out: q.estimatedAmountOut, min: q.minAmountOut };
  return { out: q.expectedOut, min: q.minOut };
}

CurveCopy Anchor Link

The curve quote carries what the program will move:

• componentTargets: the deposits, per component, in recipe order. componentFees: the fee, per component.
• componentFunding (only when you sent a wallet): per component, required, held and shortfall. A component with shortfall: "0" needs no swap.
• route (only when you sent a wallet and the deployment has a pool table): solIn, legs, venues, needsAccountSetup, transactions and a note. route absent means "not evaluated". It does not mean no route exists: that is a present route with empty legs.
• expectedOut and minOut. For a buy they are launch tokens, in base units. For a sell expectedOut is in DNA units, the internal quote unit, and must never be printed as SOL. The SOL a sell returns is route.solIn, and it is a floor.
• dnaUnitsNet is net of the fee on a buy and gross of it on a sell. A sell also carries dnaUnitsGross, the same value under the name that is true of it.
• clamped: true means the buy was cut to what remains on the curve. budgetSolIn is then the real cost of an exactInSol buy.
• completesCurve: true means this buy, filled as quoted, completes the curve.
• networkCost and tradeSettings appear where the chain has tips or priced fees.

minOut is the floor the program enforces. Below it the transaction aborts.

MarketCopy Anchor Link

A launch past the curve trades through its pools. The quote describes the route:

• routes: every spoke this size could have gone through alone, best first, with expectedOut, spreadBps, worstHopImpactBps and usable.
• hops: the swaps in order, each with label, inputMint, outputMint, amountIn and amountOut. hopDetail carries the same swaps with the pool, the venue, the impact and the fee.
• via: the component the route enters through.
• split, hubBalance and routeNote appear when a route is shared between pools, or a better one did not fit one transaction.

PoolCopy Anchor Link

A tradable collectible trades on its own pool, in one hop:

• pool, amountIn, estimatedAmountOut, minAmountOut, priceImpactBps, via.
• feeBps and feeAmount: the pool's fee rate and this trade's fee, in base units of amountIn's mint.

Fields on all threeCopy Anchor Link

The reference lists every field with its type: Quote a trade.

Test against capturesCopy Anchor Link

These shapes are pinned in the API's own test suite against responses captured from the live API, not against mocks written in the shape the author expected. Do the same: keep a capture of each shape and run your parser over it.