Get the org-wide counts the plan caps are enforced against

GET 
/api/v1/organizations/current/resource-usage

Return how many projects, API keys and webhooks the org has.

Any org member may call this, like billing-summary and for the same reason: the project quota meter renders on the dashboard, where the lowest role that can create a project is manager.

These are counts of the org, not of what the caller can see. That is the whole point — a client comparing its own visible list against an org-wide cap tells a manager they have room they do not have, and hides the wall from the person who is about to hit it.

• API-key scope required: org:read.

Responses

200

Successful Response

400

Bad request — malformed input or failed validation.

401

Missing, expired, or invalid credentials.

403

Authenticated but not authorized for this resource. Note: cross-organization reads return 404, not 403.

404

Resource not found, or hidden for tenant-enumeration safety (the caller lacks permission to know whether the resource exists).

409

Conflict — the current resource state does not allow this operation (e.g. assessment already started, email already in use).

422

Semantic validation failure — request shape was valid but contents were not.

429

Too many requests — rate limited. Retry after the window resets.

500

Internal server error — unexpected failure.