It might also be worth noting that your suggestion to go from 3 requests, to 2 by including user information in the root kraken endpoint would increase load for every single request to that endpoint, even those that only needs information about the status of a token. There could be apps that regularly check the status of their stored tokens to see if any are no longer valid, or have out of date scopes, and your suggestion would mean each time those checks are performed the API would also have to retrieve user data for every single one of those tokens being checked, which could potentially be hundreds or thousands of tokens.