Skip to main content
GET
Get the calling key, user and workspace
Returns who is calling: the acting user, the workspace the key is bound to, the payer (the workspace owner, who is charged for all work), the key’s scopes, expiry and monthly spend caps (minutes and project credits), the plan summary and its entitlements. An allow-listed view: no billing identifiers, marketing or UI-state fields. When to use: first, to learn the workspace, role and scopes before planning work. Leaked-key scanners use it to verify a key. Side effects: None. Cost: Free. Idempotency: safe and pure (never writes); retry freely. Required scopes: account:read

Authorizations

Authorization
string
header
required

API key from Settings -> API keys, sent as Authorization: Bearer <key> (SDK environment variable RASK_API_KEY). Bound to one workspace and one acting user. Operations list the scopes they need (OpenAPI 3.1 scopes on a bearer scheme).

Scopes

account:read

Response

OK: Me.

Who is calling: an allow-listed view of the acting user, workspace, payer and credential.

object
enum<string>
required

Always me.

Available options:
me
user
object
required

The acting user.

workspace
object
required

The workspace the key is bound to.

payer
object
required

The payer of the workspace.

auth
object
required

The calling credential.

plan
object
required

Plan summary.

entitlements
object[]
required

Plan features.