There are lots of things that use OkHttp.
OkHttp okhttp#1063 provides a default user-agent, but that does make it easy to figure out what is (ab)using quotas.
It's traditional for clients of libraries to fill in their own useragent (typically embedding their underlying agent w/in the field).
For a general sense of how user-agents are written, please see: https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/User-Agent/Firefox
In general, basically the syntax is:
TokenA/1.1 (platform; information; ...) TokenB/2.3 ...
The GitHub.com folks reported that the majority of my quota was spent by:
But I can't easily tell if that's:
Ideally, the user-agent would be something like:
If you expect to have issues involving the java version, then including the java version in the UA could be useful...
To get the okhttp version one can do something like: