Usage endpoints

Generated from the central API contract. Availability and permissions are checked by the connected service.

GET /v1/usage

Usage

Authorization: usage:read Current resource access and role checks also apply.

MCP: get_usage

Parameter

Location

Required

Type / values

view

query

No

string

HTTP request pattern: replace path/query placeholders and prepare any body from the linked model. Run mutations only for your intended action; session-only endpoints need their application authentication context.

curl --fail-with-body --silent --show-error -X GET \
  -H "Authorization: Bearer $GD_API_KEY" \
  "$GD_API_BASE/v1/usage"

These are the response shapes declared by OpenAPI. Permission, validation, budget and service errors can also occur; see errors and recovery. An unconstrained JSON response is not a guarantee of undocumented fields.