Skip to main content
Illustrative values. The amount, makerBps, takerBps, and feeRateBps numbers shown in examples on this page are illustrative. The authoritative rates for your account are always the live values returned by /api/me/fees and /api/me/fee-tier — read them before signing. See Fees for the formula.

​
Fee ledger entries

Each trade produces FeeLedgerEntry rows — one per role (maker / taker). In PS_QUADRATIC_V1 the maker role is always 0.
Reverse-chronological. Paginate with the opaque cursor echoed back as nextCursor. limit is capped at 500 (default 100). Response:

​
Pagination

Keyset-paginated, same scheme as Trades: each response carries an opaque nextCursor — pass it back as ?cursor=<nextCursor> for the next (older) page. nextCursor is null only on the last page. limit caps the page (max 500, default 100). The legacy ?before=<ISO-8601> still works but cursor is preferred (unique tiebreaker — a single match writes both the maker and taker fee rows with the same createdAt, so a timestamp-only cursor would skip one at a page edge).

​
Fee tier

Response:

​
Reconciling against on-chain

Once on-chain settlement is wired, each fee ledger row gets a txHash field pointing to the settlement transaction.