When doing a browse request, the count and offset keys are prefixed by the entity name, for example "recording-offset" and "recording-count".

It makes deserialization harder. If it was just "offset" and "count", the JSON response could be handled like a search request.

I guess this is intended, so feel free to close this issue. I was just wondering why this is done?

Example:
https://musicbrainz.org/ws/2/recording?artist=b071f9fa-14b0-4217-8e97-eb41da73f598&fmt=json

Returns:

{"recording-offset":0, "recording-count":8173, "recording":[...]}

Expected:

{"offset":0, "count":8173, "recording":[...]}