Skip to main content
GET
/
api
/
me
Current user
curl --request GET \
  --url https://archyon.app/api/me \
  --header 'Authorization: Bearer <token>'
{
  "id": 123,
  "displayName": "<string>",
  "isAdmin": true,
  "provider": "<string>",
  "createdAt": 123,
  "session": {
    "isApiToken": true,
    "orgId": "<string>",
    "orgRole": "<string>",
    "orgSlug": "<string>"
  },
  "login": "<string>",
  "avatarUrl": "<string>",
  "lastLoginAt": 123
}

Documentation Index

Fetch the complete documentation index at: https://docs.archyon.app/llms.txt

Use this file to discover all available pages before exploring further.

Authorizations

​
Authorization
string
header
required

Both Clerk session JWTs (browser) and Archyon Personal Access Tokens (an_pat_…, server / CLI / MCP) use the same Bearer header. The server distinguishes them by token shape.

  • Clerk JWTs carry org context in the token claims (org_id, org_role, org_slug) — required for org-scoped endpoints. Configure your Clerk session template to include these claims; see DEPLOYMENT.md.
  • PATs are minted at /account → Tokens. Each PAT is bound to whichever org was active at mint time. Switch orgs and re-mint to address a different org.

Response

OK.

​
id
integer
required
​
displayName
string
required
​
isAdmin
boolean
required
​
provider
string
required

Identity provider (e.g. clerk, github).

​
createdAt
integer
required
​
session
object
required
​
login
string | null
​
avatarUrl
string | null
​
lastLoginAt
integer | null