Back to Blog
Sep 15, 2026·Efe·5 min read·Update

Introducing Workspaces and Auth Tokens

Audaxic now organizes projects into workspaces — every account starts with one called Default — and adds scoped auth tokens for programmatic project and API key management. If you're an existing user: your projects were moved automatically, nothing broke, and there's nothing you need to do.

What are workspaces?

As projects pile up — client work, side experiments, production apps — one flat list stops working. Workspaces group your projects: switch between them in the dashboard sidebar, and the Projects, API Keys, and Auth Tokens pages each show the active workspace. Create more any time for clients, environments, or teams.

New accounts get a Default workspace automatically. Existing accounts already have one too — every current project was moved into it during the upgrade, with keys, memories, and billing untouched. Limits are counted per account across workspaces: up to 500,000 projects and 1,000,000 API keys — enough to provision per-user projects and keys programmatically in your own app.

Auth tokens in two minutes

Auth tokens are for automation: CI pipelines that spin up preview projects, scripts that provision keys, anything you'd rather not click through. Create one on the dashboard's Auth Tokens page — pick a name, tick the permissions it needs, and copy the at_… token. It's shown once, identified by prefix afterwards, and revoking is one click.

Four granular scopes control what a token can do: projects:read, projects:write, keys:read, keys:write. A read-only CI token, for example, can list projects but can't create or delete anything. A few calls to get started:

# List projects in the token's workspace
curl https://memory-api.audaxic.com/api/projects \
  -H "Authorization: Bearer at_your_token_here"

# Create a project (lands in the token's workspace)
curl -X POST https://memory-api.audaxic.com/api/projects \
  -H "Content-Type: application/json" \
  -H "Authorization: Bearer at_your_token_here" \
  -d '{"name": "ci-preview-123"}'

# Create an API key for it
curl -X POST https://memory-api.audaxic.com/api/api-keys \
  -H "Content-Type: application/json" \
  -H "Authorization: Bearer at_your_token_here" \
  -d '{"name": "preview-key", "project_id": "proj_..."}'

Full reference lives in the docs.

Scoped by design

Tokens are confined to one workspace: without the right scope you get 403, and other workspaces answer 404 as if they don't exist. Tokens can never create, list, or delete other tokens — that stays behind your dashboard login. And the two credential types never cross: ak_… keys store and search memories, at_… tokens manage projects and keys. An auth token sent to the memory API gets a 401, by construction.

One honest limitation: workspace deletion isn't in this release — you can delete projects and tokens freely, but workspaces themselves stay put for now. It's on the roadmap.

FAQ

Do I need to move my existing projects?

No. Every existing project was automatically moved into a workspace called Default. Your keys, memories, plan, and billing are exactly as they were.

Do auth tokens cost extra?

No. Tokens are free — they operate within your existing plan limits and just let you manage the same resources programmatically.

Can I delete a workspace?

Not yet. Delete individual projects and tokens any time; workspace deletion is coming in a later update.

Try it now. Open the Auth Tokens page, mint a token, and automate something. Related: import past conversations · Why Your Coding Agent Forgets Conventions

Written by Efe — Sep 15, 2026 · More articles · X @AudaxicTech