There is the group limit (the limit on the number of groups a tenant have, which should be at `/v1.0/<tenantId>/limits`), and the limit on the number of policies per group (which if we were giving the number of policies remaining to the group, I agree would make sense to be at `/v1.0/<tenantId>/groups/<groupId>/limits`, and then the number of webhooks per policy could be at `/v1.0/<tenantId>/groups/<groupId>/policies/<policyId>/limits`.

Repose only points to one endpoint though for absolute limits, and it interpolates those absolute limits with the rate limits.  Looking at [load balancer docs](http://docs.rackspace.com/loadbalancers/api/v1.0/clb-devguide/content/Determining_Limits_Programmatically-d1e1039.html), it looks like they do not use repose, but they also keep all the limits on one page even if it's a limit per load balancer.

Looking at the [nova docs](http://docs.rackspace.com/servers/api/v2/cs-devguide/content/ProgrammaticLimits.html), it looks like all their limits are on one page interpolated with the rate limits (in a repose-like manner), including the max per something (e.g. maxImageMeta).

I'm not sure what would be cleaner - having 3 apis that need to be hit to get the limits, 1 of which may or may not be is interpolated with the rate limits, or having 1 with just the absolute numbers and not necessarily what the user has currently used.