List your per-trade BuilderCodes earnings

Ed25519 session-key request signing. Every authenticated request carries three headers: X-Monaco-PublicKey (64-char lowercase-hex session public key), X-Monaco-Timestamp (Unix milliseconds, within 30s of server time), and X-Monaco-Signature (hex ed25519 signature). The signature is over METHOD\npath?query\ntimestamp_ms\nSHA256_hex(body), where the body hash is the SHA-256 of the empty byte string when there is no body. Obtain the session keypair from POST /api/v1/auth/challenge followed by POST /api/v1/auth/verify.

Items per page (max 1000)

Pagination cursor with two states:

• Omitted or empty string (""): start a cursor walk with no prior position, from the newest credit.
• Non-empty: an opaque cursor from a previous response's next_page_token; results resume immediately after that position.

The walk seeks on (created_at, id) descending, served by idx_buildercode_payouts_application_created_id, whose leading key is the caller's own application and whose remaining keys are this seek's, both descending. Both key columns are NOT NULL and fixed for a credit's lifetime. (Spelled without the column list on purpose: the read contract test asserts this request message never mentions a caller-selected identity.)

This REPLACES the removed mode's (sequence, sequence_ordinal, created_at, id) order, whose two leading columns are nullable — no backfill exists for credits written before they did — and a nullable leading key cannot be a total cursor key: the NULL rows sort together at one end, and a seek through them would need a COALESCE no index covers.

ORDERING CHANGE, not just a pagination change. The new key is total and stable — a page can neither skip nor duplicate a credit — but it is NOT chronological inside one persistor batch. created_at defaults to NOW(), which is transaction-start time, so every credit one batch writes shares an identical timestamp; the id tie-break defaults to gen_random_uuid(), which the persistor leaves alone. So within a batch the order is arbitrary and a LATER fill can be listed ahead of an earlier one. The removed order led with sequence and sequence_ordinal precisely because those carry the engine's fill order, and one entry routinely holds several credits (a taker sweeping N makers, or a flattened BatchCreateOrders). Preserving fill chronology would need those columns backfilled first, which is not possible for credits written before they existed. Across batches the order is still newest-first.

total and total_pages are populated and exact, and count the rows the kind filter selects. Filters must match the request that produced the token, or the request is rejected 400.

Only return BuilderCodes payouts of this payout kind: REVENUE_SHARE (the frontend's share of Monaco's fee), BUILDER_FEE (builder fees charged to takers) or BUILDER_MAKER_FEE (maker add-ons charged to makers). Both builder-fee kinds are credited to the enrolled application whose order paid them. Omit for every kind.