---
title: "Describe the current token."
method: GET
path: "/v1/me"
tags: ["Account"]
---

# Describe the current token.

`GET /v1/me`

## Request

- Base URL: `https://api.scalix.world`
- URL: `https://api.scalix.world/v1/me`
- Auth: HTTP bearer

Returns the caller's identity, effective permissions and scopes, the MCP
tools their scopes unlock, and their plan's rate-limit and API-key ceilings.

## Response `200`

The caller's identity, permissions, MCP tools, and plan limits

- MeResponse: Response for `GET /v1/me` — identity, permissions, available MCP tools, limits.
  - `identity` MeIdentity, required: Token identity (key, type, tenancy, creator).
    - `key_id` string, required
    - `token_type` string, required
    - `org_id` string, required
    - `project_id` string, nullable
    - `created_by` string, required
  - `permissions` MePermissions, required: Effective permissions for the caller's token.
    - `role` string, required
    - `scopes` string[], required
    - `can_create_keys` boolean, required
    - `can_create_projects` boolean, required
  - `tools` string[], required
  - `limits` MeLimits, required: Plan-derived limits (advisory — see `api_key_limit_for_plan`/`rate_limit_for_plan`).
    - `plan` string, required
    - `rate_limit_rps` integer, required
    - `api_keys_max` integer, required
    - `connected_apps_max` integer, required: OAuth-granted connected apps (ChatGPT, Claude, an IDE …). A separate pool from `api_keys_max` — see `plan_limits::connected_apps_for_plan`. Reported so the console reads the limit from the server that enforces it, rather than from a client-side constant that can drift out of step.

## Other responses

- `401`: Missing or invalid token
- `500`: Internal error

---

[API](https://skmtc.dev/scalix/apis/scalix-cloud-api.md) · [All operations](https://skmtc.dev/scalix/apis/scalix-cloud-api/llms.txt) · [OpenAPI document](https://skmtc.dev/scalix/apis/scalix-cloud-api/revisions/2c04ca0a90bb?raw)