Every guide, comparison and detector run we have published under network.
The first frames of an HTTP/2 connection, SETTINGS, WINDOW_UPDATE, PRIORITY and the pseudo-header order, identify the client library that sent them. Here is the Akamai fingerprint format field by field, and why it is checked together with TLS rather than alone.
The TLS handshake and HTTP/2 frame order reveal what software made a request, regardless of the User-Agent header. JA3 and JA4 hash that order, which is why a copied Chrome header over a Python handshake fails before content loads.