identity
name: identity
description: onboard as an agent or user — create an identity, get a token, and start working with zero frictionsublimated uses progressive identity. no signup forms, no OAuth flows required. start working immediately, add identity details later to unlock more capabilities.
quick start (zero friction)
POST https://id.sublimated.com/api/auth/signupreturns:
userId— your identityspaceSlug— your personal space (auto-created)token— scoped access token (sk_...)
you can now push data, create items, and use the API. no email, no password, no verification needed.
using your token
API:
Authorization: Bearer sk_xxxgit:
git clone https://me:sk_xxx@sublimated.com/{your-space}.gitthe token works for both. username in git URL can be anything.
trust levels
every user starts at level 0 and upgrades by providing more identity:
level 0: anonymous — token only, personal space, 100MB storage, 30d expiry if unclaimed
level 1: email verified — persistent, no expiry, notifications
level 2: identity linked (GitHub, etc.) — discoverable, named space
level 3: full account — email + username + linked identity
level 4: system only — internal service accounts, agents never reach this
upgrade anytime:
PATCH https://id.sublimated.com/api/me
{ "email": "agent@example.com" }what each level unlocks
level 0: push to own space, read public spaces, basic API access
level 1: no expiry, email notifications, can be invited to other spaces
level 2: discoverable profile at
sublimated.com/{username}, can create org spaceslevel 3: full platform access, billing, admin roles
creating additional tokens
POST https://api.sublimated.com/v1/spaces/{slug}/tokens
{
"label": "ci-deploy",
"permissions": ["read", "write"],
"pathScope": ["src"],
"expiresIn": "30d"
}tokens can be scoped by permissions, paths, branches, and expiry.
key management
register public keys for SSH access:
POST https://id.sublimated.com/api/keys
{ "publicKey": "ssh-ed25519 AAAA...", "label": "my-key" }discover keys by username:
GET https://id.sublimated.com/keys/{username}agent onboarding pattern
POST /api/auth/signup— get identity + space + tokenpush data to your space via git or API
optionally upgrade identity later for persistence and discoverability
no human approval needed at level 0. agents and humans use the same identity system.
see also
spaces — what you get when you create an identity
git-workflow — use your token to clone and push
data-api — use your token to call the REST API