List the RFQ requests visible to the caller, newest first. A request is visible
when the caller raised it, when it is addressed to the caller, or when the caller
has already quoted on it.

Once a request is accepted it stays in every addressed user's feed, but only the
two trade parties see settlement detail. Everyone else sees status: filled (or
cancelled if the trade was voided) with no trade_id, leg status, settlement
transaction id, or funding flags.

Pass asset_class=crypto,commodity,equity to list spot requests only. All filters
narrow the caller's visible requests; they never widen them.

Time range and paging. There is no default time window: without since the
feed covers the caller's whole history. Pass since=24h for the last 24 hours, or
an RFC 3339 time to start from. Results are paged newest first: read limit
requests at a time (default 100, at most 200), and pass the response's
next_cursor as cursor to fetch the next page while has_more is true. Pages
stay stable while new requests arrive.

Rolling window. since=24h is resolved against the time of the call, so each
fresh first page (no cursor) covers the 24 hours before that moment. The
response echoes the resolved window as since, and next_cursor carries it: while
scrolling, the window stays where the first page put it, even if since=24h is
sent again. To show a count that matches what can be scrolled to, pass the echoed
since to GET /api/rfq/requests/counts. With a status filter a page can come
back short, or has_more can be true before an empty last page, because phases
are derived after the query; keep following next_cursor until has_more is
false.