Accounts and Workspaces
Start on your own. Add stored memory or bring a team when you need it.
You can use Augenta on your own. Sign in, open your personal account, create an API key and make your first request. Creating an organization or assigning a Workspace is optional.
Your personal account
Your personal account holds your API keys, credits and any Workspaces you create. The user menu at the top right contains your profile, account settings, credits and billing, and account switching.
Start with an API key with no Workspace assignments: a one-shot request processes its input and returns the memory it forms, and nothing is stored. Use a Workspace when your agent needs memory that later calls can recall.
Workspaces hold stored memory
A Workspace is where Augenta stores experiences and makes them available to future requests. Create or choose one when your application needs managed memory, then select it when creating an API key. The same key can still make stateless requests.
| Key permissions | What you can do |
|---|---|
| No assigned Workspaces | Make stateless requests without storing memory in Augenta. |
| One assigned Workspace | Also read and write stored memory in that Workspace. |
| Multiple assigned Workspaces | Also read and write any of those Workspaces, selecting one per request. |
Workspace membership controls who can read its memory. Workspace admins manage members and the synthesis schedule. For the complete request flow, see Using the APIs together.
Add an organization later
An organization gives a team a shared account with its own credits, keys, Workspaces and members. Open your user menu → Add an organization to request setup. Once invited, sign in with the same email; the organization appears in Switch account. Your personal account stays available.
Organization setup is currently assisted. Joining or switching accounts does not transfer credits, API keys or memory between them. A key always belongs to the account where it was created.
Organization owners and admins manage their account and administer its Workspaces. Other members use the Workspaces they have access to; each request is still checked by the API.
Connectors are for connected sources
The API quickstart does not require a Connector. A Connector links a project or integration to a Workspace, for example when a coding-agent plugin captures experience. You can add that integration after your first API call. API authentication explains existing Connector keys.