---
title: "Get Current Key Info"
method: GET
path: "/api/v1/auth/keys/me"
tags: ["Authentication"]
---

# Get Current Key Info

`GET /api/v1/auth/keys/me`

## Request

- Base URL: `https://cryptodataapi.com`
- URL: `https://cryptodataapi.com/api/v1/auth/keys/me`
- Auth: API key in header `X-API-Key`

Get information about the current API key.

Shares key_limits_block with the mint and /resend-verify, so the three
surfaces cannot disagree about what this key may do.

Reports the EFFECTIVE limits (limits_for), not the tier's headline numbers —
a free key whose email is unverified is on the smaller starter allowance, and
a dashboard or agent that showed the tier default would be promising quota
the limiter won't honour.

## Response `200`

Successful Response

- APIKeyInfo: API key information (without the full key).
  - `key_prefix` string, required
  - `email` string, required
  - `tier` string, required
  - `is_active` boolean, required
  - `requests_today` integer, required
  - `daily_limit` integer, nullable, required
  - `created_at` string, date-time, required
  - `expires_at` string, date-time, nullable, required
  - `per_minute_limit` integer, nullable
  - `email_verified` boolean
  - `verified_daily_limit` integer, nullable
  - `upgrade_message` string, nullable
  - `rate_limit_scope` string, nullable
  - `upgrade` object, nullable

---

[API](https://skmtc.dev/cryptodataapi/apis/crypto-data-api.md) · [All operations](https://skmtc.dev/cryptodataapi/apis/crypto-data-api/llms.txt) · [OpenAPI document](https://skmtc.dev/cryptodataapi/apis/crypto-data-api/revisions/8628b754ca81?raw)