Skip to content

Introspection

GET /v1/me

Returns the user, organization, and token metadata behind the current connection. The simplest way to confirm a token is valid and see what it resolves to. The API sees exactly what this user can see, evaluated live on every request.

Terminal window
curl https://api.mereon.ai/v1/me \
-H "Authorization: Bearer $MEREON_TOKEN"
{
"user": {
"id": "usr_8s2k...",
"name": "Alex Doe",
"email": "alex@acme.com"
},
"organization": {
"id": "org_3a1p...",
"name": "Acme Inc"
},
"token": {
"name": "Claude on my laptop",
"tokenPrefix": "mrn_8s2k",
"scopes": ["read"],
"expiresAt": "2026-09-15T00:00:00.000Z"
},
"features": ["public-api", "pii-redaction"],
"permissions": ["video.create.organization", "guide.create.organization"]
}
Field Type Notes
user.id string The connected user’s id.
user.name string Display name.
user.email string | null Email, when available.
organization.id string The organization the token is pinned to.
organization.name string Organization display name.
token.name string The name you gave the token at creation.
token.tokenPrefix string The first characters of the token, for identification.
token.scopes string[] What this credential may do: read, and content:write for uploading. A personal access token is issued read only; an OAuth token holds whatever was consented to.
token.expiresAt string | null ISO 8601 expiry, or null if non-expiring.
permissions string[] What the connected user may do, as resource.action[.scope] strings, resolved live on every request. Check this before offering a write: a credential holding content:write still cannot do anything its user is not permitted to do.
features string[] Product features this organization is entitled to. Distinct from token.scopes: scopes are what the credential may attempt, features are what the organization bought. Read this to decide what to offer rather than hardcoding an assumption. The set grows over time, so treat an unrecognised entry as something to ignore rather than an error.