Hi Michael, it does seem like a misleading error.
However, because we cannot change the scope of the user once its been created, it is possible that in case of granular access, the API username is being rendered invalid because there is no about.json file.