GET /api/whoami — identity check

​

Endpoint

GET /api/whoami

​

Authentication

​

Response

{
  "user": {
    "id": "u_abc123...",
    "email": "you@example.com",
    "role": "user",
    "tier": "pro",
    "approved": true
  }
}

​

Use cases

• Pre-flight validation — call this before any expensive workflow run to confirm your key works without paying for a real execution.
• Tier-aware routing — branch your script depending on the tier (skip Business-only models if user.tier === 'pro').
• CI smoke test — assert user.approved === true and user.email matches the expected account before production deploys.

​

Example

curl https://knouds.ai/api/whoami \
  -H "x-api-key: $KNOUDS_KEY"

import os, requests
me = requests.get('https://knouds.ai/api/whoami',
                  headers={'x-api-key': os.environ['KNOUDS_KEY']}).json()
print(f"Logged in as {me['user']['email']} (tier: {me['user']['tier']})")

const me = await fetch('https://knouds.ai/api/whoami', {
  headers: { 'x-api-key': process.env.KNOUDS_KEY },
}).then(r => r.json());
console.log(`Logged in as ${me.user.email} (tier: ${me.user.tier})`);

​

Notes

• For richer identity (credit balance, top-up balance, business status, onboarding state) the session-only endpoint /api/me returns more fields. That endpoint requires a browser session cookie and rejects API keys.
• A 401 response means the key is missing, revoked, or pre-Phase-11 (see LEGACY_KEY_RETIRED).