Everything on this page is read out of this browser's own storage for this app.
Nothing here is fetched from anywhere except a single call to /me to tell you whose
session it is. No token is ever sent anywhere else, and this page cannot see tokens belonging to
any other app.
Checking…
| Subject type | — |
|---|---|
| Subject id | — |
| Credits | — |
| Storage key | — |
A guest session has no balance and cannot run either lane, though the
whole free surface — layouts, your own captions, the typesetting, the PNG export — works
without one. /me returns exactly three fields, subject_type,
subject_id and credits, so "signed in" means
subject_type reads user, and nothing else.
This token can spend the credits of whoever it belongs to. Treat it like a password: keep it in a secret store, never in a repository, and never in a page you ship to other people.
Forget it on this device deletes the copy in this browser and nothing else. It is not revocation: the token string stays valid until it expires on its own, so a copy you pasted somewhere else keeps working. If a token has genuinely leaked, rotate it from your SkillSafe account rather than here.
Take a fresh guest token discards the current one and mints a new guest identity. Anything stored against the old guest belongs to that identity and will not follow you across.
Send it as a bearer token against https://api.skillsafe.ai/v1/app-api. The token
identifies the app as well as the caller, so there is no slug header to set.
curl -s "https://api.skillsafe.ai/v1/app-api/me" \
-H "Authorization: Bearer $MEME_GENERATOR_TOKEN"The full walkthrough, in eight languages, is on the API page.