Getting started / Quickstart

Quickstart

Setup is a guided, chat-style wizard at app.agenticwebteam.com/onboarding. Every step saves automatically — you can leave at any point and resume by signing back in.

1. Sign in with your email

Enter your work email and we send a 6-digit sign-in code. There are no passwords — you'll use the same one-time code flow every time you sign in.

The 6-digit code from your inbox is your sign-in code. Your AWT invite code (AWT-XXXXXXXX) is a different thing and comes next.

2. Invite code & organisation

Creating a workspace needs an AWT invite code. If a partner or an Agentic Web Team contact gave you one, enter it. If not, click “Don't have a code? Get one instantly” under the code field and one is issued to your verified email on the spot.

Then tell us who you are: your name, your organisation's name and (optionally) your website domain. This creates your private workspace.

3. Choose a plan

Pick a tier — Starter, Growth or Scale (see Plans & credits) — and subscribe through Stripe Checkout. Billing starts today and your first month's included credits are available immediately; cancel any time and billing stops at the end of the period. Want to see the assistant working before you subscribe? Book a demo on a live site.

Larger organisation? Choose Apply for Enterprise instead — invoice billing, human onboarding and custom terms; we reply within one business day and you can keep connecting your systems meanwhile.

4. Connect your systems

Three connection steps follow. Only the CMS is essential for a useful assistant; the rest are skippable and land on a checklist you can finish later.

  • CMS (recommended now) — pick your platform and paste its API credentials. Every connection is tested live before it's accepted, and tokens are stored encrypted (AES-256). Full per-platform instructions and minimum version requirements (e.g. WordPress 5.6+ over HTTPS): Connect your CMS.
  • Repository (optional) — lets the assistant make code changes. GitHub, GitLab and Bitbucket are supported; grant access to just your site's repo. See Connect your repository.
  • Hosting (optional) — how your site rebuilds. If your host rebuilds on git pushes you're already covered; a deploy-hook URL additionally lets the assistant trigger rebuilds. See Hosting & deploys.

You can also invite colleagues by email at this point — they get access straight away, and fine-grained roles can be set later in Team settings.

5. First run

One click: the assistant introduces itself by reading your connected content — a real run through the full system, so you know everything works end to end. Completing it activates the workspace and drops you into the portal, ready for your first request:

you › What content do we have, and what would you improve first?

Help along the way

A Setup help chat sits in the corner of the wizard the whole time — ask it anything about the steps, where to find an API key, or how your credentials are handled. It's guidance only: never paste keys or passwords into any chat; credentials go only in the wizard's masked fields.

Stuck on a credential your developer manages? Skip the step, invite them in the Team step, and they can finish the checklist from their own sign-in.