Workspaces and teammates on the API platform
This page takes you from no account to a working SynapseX API platform workspace that you can put a teammate into. When you finish you will have an account, a workspace you own, and a clear picture of what that workspace holds — which matters, because the workspace, not you, owns every API key and every dollar of credit.
This is the developer product at platform.synapsex.ai . It is separate from SynapseX Chat: see Accounts, plans and billing.
How do I create a SynapseX API platform account?
- Go to platform.synapsex.ai/auth/register .
- Either fill in your name, email and a password of at least 8 characters and submit, or click Continue with Google.
- You are signed in and land on the dashboard. Your personal workspace has already been created for you.
Two things to know about signing in afterwards:
- Sessions last 60 minutes. You will be asked to sign in again after that.
- Five failed sign-in attempts lock the account for 15 minutes. Wait it out rather than retrying.
What is a workspace and why does it matter?
A workspace is the billing and ownership boundary for everything on the API platform. The workspace owns:
- every API key, including keys created by other members;
- the credit balance;
- the monthly spend limit and the spend alert thresholds;
- every usage and request record.
Your individual user account owns none of those things — it is only a way to sign in and be granted a role in a workspace.
The practical consequence: a key created by one member spends the shared workspace balance and appears in the shared usage view. If you want two things billed and tracked apart, put them in two workspaces.
Your first workspace is created automatically on first login, named after you, and you are its OWNER.
When should I create an additional workspace?
Create another workspace when you want a hard separation of credits, keys and usage reporting. Typical reasons:
- Environments. A production workspace and a staging workspace, so a runaway test job cannot burn the credits your live service needs.
- Clients or projects. One workspace per client, so each one’s usage report is exactly that client’s usage and nothing else.
Create one at /dashboard/settings/workspaces by giving it a name. You
become its OWNER, and the new workspace starts with its own empty balance and no
keys — nothing is copied across from your first workspace.
How do I give a teammate access?
No invitation email is sent. Your teammate must already have a SynapseX platform account. Adding an email address that has no account fails with the message “No SynapseX account exists for that email yet. Ask them to sign up first.” Send them to platform.synapsex.ai/auth/register before you try.
- Ask your teammate to sign up and tell you the email address they used.
- Go to
/dashboard/settings/members, add that email and choose a role: ADMIN or MEMBER. - Access is granted immediately. There is no pending state and nothing for them to accept — the workspace simply appears for them next time they sign in.
Adding someone who is already a member is refused with HTTP 409.
Who can do what?
| Action | OWNER | ADMIN | MEMBER |
|---|---|---|---|
| Add or remove members | Yes | Yes | No |
| Change workspace settings (name, slug, domain) | Yes | Yes | No |
| Use the workspace’s keys and credits | Yes | Yes | Yes |
Only owners and admins can manage the workspace; a member who tries is refused with HTTP 403 and the message “Only owners and admins can add members.”
What next?
Your workspace is not usable until it has both a key and credits:
- Create an API key — the
sk-synapsex-…credential your code will send. - Add credits — with a zero balance, every API call is refused with HTTP 402 before any model runs.
Then make your first call: Platform API authentication.