Getting started
A step-by-step guide to creating a team workspace, inviting your team, making your first API key and starting your first chat
Getting started
Welcome! This guide walks you through the four things worth doing on your first day: create a team workspace, invite your teammates, make your first API key, and start your first chat. If you are new here, that is all you need.
Coming from the email? Your sign-in link is valid for 10 minutes.
Step 1 — Create your team workspace
The first time you sign in, we ask you to create a team workspace. That is where your team's API keys, usage and billing live.
- Pick a name people will recognise — "Aban Studio", say. It appears in the header and in the emails your teammates receive.
- You can rename it later, so don't agonise over it.
- Names are limited to 218 characters.
You become the workspace's Owner. Owner is the only role that cannot be given to someone else and cannot be removed; if you want to hand the whole thing over, create a new workspace.
Step 2 — Invite your team
Go to Members and choose "Invite member".
- People who already have an account are added immediately and have access on the spot.
- People who do not have one yet get an invitation email, valid for 72 hours.
If an email doesn't arrive, the pending invitations list lets you resend it or withdraw it. If it still doesn't arrive, copy the link and pass it on however is easiest — chat, phone, in person.
Pick each person's role up front
| Role | Good for | What they can do |
|---|---|---|
| Owner | Founder, final decision-maker | Everything, including deleting the workspace |
| Admin | Operations lead | Invite, change roles, remove members, create team keys |
| Finance | Whoever owns the budget | Wallet, deposits, USD figures, financial reports |
| Member | Everyone else | Create their own personal key and use chat |
You can change a role later — you do not have to get it right the first time.
Step 3 — Make your first API key
Go to API keys and choose "Create API key".
A workspace needs at least $5 in credit before a key can be created: without credit the gateway will not route a single request. If you are short, the page explains this and offers to take you to the wallet.
Important: the key is shown once, in full. Save it somewhere safe at that moment. If you lose it, revoke it and make a new one.
Keep it in your project's environment, never in GitHub or anything public.
A first request:
curl https://api.aize.dev/v1/chat/completions \
-H "Authorization: Bearer $AIZE_API_KEY" \
-H "Content-Type: application/json" \
-d '{"model": "GLM 5.3 Flash", "messages": [{"role": "user", "content": "Hello!"}]}'Step 4 — Start in chat
Head to Aize Chat — where you talk to models, add connectors, and build your own assistants.
- Workspace: switch between your personal workspace and your team's at the top of the page. Each workspace's conversations belong to that workspace.
- Connectors: connect Divar, GitHub, Drive and your own internal services — so the models do not just answer, they actually act.
- Sharing: any conversation can be handed to a colleague with one link, which you can revoke later.
Step 5 — Keep an eye on it
- Usage & analytics: daily charts, broken down by model and by person, in USD with Gregorian dates.
- Audit log: every key created or revoked, every member added or removed, with who and when.
If you run low, you are told where you stand — you do not have to watch for it.
Habits worth forming
- One key per job. If one leaks, you revoke that one and everything else keeps working.
- Set a monthly limit per key. A key called in a loop by mistake stops there rather than eating the whole budget.
- Share assistants with the team. One good assistant carries knowledge from person to person.
- If something does not work, use "Contact support" in this panel and send the error code — it tells us far more than a description does.
Start now
You are ready. For more detail see Members, Wallet and API keys.
Glad you are here. 🌱