mak_ admin key — see Admin Keys for minting, scopes, rotation, and expiry.
403, whatever the route.
Only six routes on this page appear in the API Reference tab:
POST /v1/usage, POST /v1/usage/events, POST /v1/usage/rejections, GET /v1/usage/events/{event_id}/attempts, GET /v1/usage/rate-limits and GET /v1/usage/spend-trend. Everything else here — keys, org, members, billing, alerts, webhook deliveries, routing-policy templates, provider keys, analytics, logs, the CSV export and the two org spend routes — is withheld from the published spec, so this page is its reference.Scope, in one line
Each route also has a minimum scope — the narrowest key that reaches it. Aself-scoped key reaches only rows it owns; org reaches the whole organization.
Eight permissions act on the organization itself and can therefore only be granted at org scope: org:read, org:write, alerts:read, alerts:write, limits:read, limits:write, logs:read, logs:read_bodies. Asking for them at self or team is a 422 at mint time.
Of the rest, only keys:read, keys:write and provider_keys:read do anything below org scope. members:write, billing:read and usage:read can be granted narrower, but every route that reads them requires org — so a self-scoped key carrying one gets a 403 rather than a narrower answer. Grant those at org or not at all.
API keys
Manage thersk_ inference keys your applications call models with.
A key minted by an admin key belongs to that key’s lineage, not to a person, and survives rotation of the admin key that created it. See Admin Keys for what that means for ownership and billing.
Organization
Members and invitations
Usage
Seven of these also accept anrsk_ key carrying the usage:read scope. Three do not — the CSV export and the two org spend routes take an admin key or a dashboard session, and an rsk_ bearer gets a 401. They are marked below.
GET /v1/usage/requests/{request_id} — the single-request lookup — is the one usage route an admin key does not reach. It takes an rsk_ key with the usage:read scope. Usage API covers the request and response shapes for this group.Analytics
The analytics surface reads the same traffic as the usage group, pre-aggregated. The sameusage:read permission at org scope opens it, and an admin key reads the whole organization’s traffic here — unlike an rsk_ key, which sees only its own rows.
Reads only. Creating, updating and deleting a saved view is refused to any key, admin key included — saved views are managed from a dashboard session.Analytics is rolled out per environment. Analytics API documents the dimensions, measures and query shapes.
Billing
Alerts and notifications
Alert channels, the policies that fire into them, and the outbound webhook delivery log. See Notifications for the event catalogue and payload shapes.These paths are
/alerts/..., not /v1/alerts/....Webhook deliveries
Routing policy templates
Shared retry and fallback policy that keys reference instead of each carrying their own. See Retry and fallback.Creating a template is a dashboard action. An admin key can read and edit templates but cannot create the first one.
Provider keys
This is a read of the catalogue, not of your credentials. Adding, listing or removing your own BYOK keys is a dashboard action — see Bring your own key.
Logs
A Loki-compatible read of your organization’s own log tenant, so you can point your Grafana at Mesh directly.logs:read covers the query surface; logs:read_bodies additionally serves stored request and response bodies.
Setup, fields, queries and limits: Request Logs.
Reads are capped per organization per minute. Records older than 7 days are not returned.
What an admin key never reaches
Errors
API errors covers the error envelope.
Related
- Admin Keys — minting, permissions, scope, rotation, revocation
- Authentication —
rsk_againstmak_ - API Keys — the inference keys this API manages
- Usage API — request and response shapes for the usage group
- Notifications — the event catalogue behind alerts and webhooks