# Get your first verification in 5 minutes

> Follow the first steps from signing up to getting your first verification result — all in under five minutes. You'll create a workspace, ask your AI to make a test, and get back the result of the AI clicking through it for you.

## 1. Sign up and get 60 credits

First, create an account with [Start for free](/en/docs/quickstart). There are three ways to sign up.

- Sign up with email and password
- Sign up with your Google account
- Sign up with your GitHub account

If you sign up by email, a verification email arrives at the address you entered. Click the link inside to finish verifying. With Google or GitHub, this step is handled automatically.

Once you're signed up, **60 credits land right away.** A credit is the point you spend for the work the AI actually does. No credit card needed — you can run your first verifications immediately with the credits you got.

## 2. Create a workspace (workspace)

The first time you log in, you'll see your **workspace** — the home for your workspaces and tests. Create your first workspace here.

A workspace only needs two things.

- **Title** — the name of the service you want to check (e.g. "Our Shop")
- **One-line description** — a quick summary (e.g. "an online shop that sells clothes")

In the pricing pages, a workspace is counted as a unit called a **workspace**. Every account gets one workspace, on every plan. To start a different app, delete the workspace you no longer need first.

## 3. Connect your AI (one time)

Making tests is something **your AI does for you.** Connect Specnote once to the AI coding tool you already use — Cursor or Claude Code — and then just telling that AI "make a test for this" creates the test. The old "Create" button (an input form) inside the web app is gone; now you make tests through your AI this way.

You only connect once. It's either a single "Allow" click in the browser, or issuing a token from My Page and pasting it in. Tool-by-tool steps are in [Connect Your AI (Install MCP)](/en/docs/install-mcp), so if this is your first time, open that page, finish connecting, and come back.

> Running a verification and reading results happen right here in the web app. **Only creating a test** goes through your AI.

## 4. Ask your AI to create your first test

Once connected, just ask — **in plain words** — for what you want to check. Don't overthink it. Write, in one sentence, the thing you'd normally check by hand, and hand it to your AI.

> Make a test in Specnote for "a welcome email should arrive after signup." The workspace is Our Shop.

Say it like that, and your AI doesn't lock in the test right away — it first shows you a **plan review (a PRD)** of what it will verify and by what rules. Because Specnote browses the real screens to fill in the steps, that one sentence usually unfolds into steps like these.

1. Open the signup page
2. Enter email and password
3. Complete signup
4. Confirm the welcome email arrives

Once you skim that plan review on screen and **approve** it, your AI submits the test for real and **the first verification runs automatically.** Verification only starts after you've confirmed _what_ will be checked — the AI never runs off on its own. (Only a person can approve. Tell your AI to "approve it" and it refuses, handing back the approval screen's address instead.)

Here's one tip: ask for **one thing at a time.** Rather than cramming "check signup and payment and notifications all at once," the more clearly you name a single thing you want to check, the more accurate the resulting test.

The five steps a test goes through, and how to make the plan review more accurate, are covered in [Creating tests](/en/docs/creating-scenarios). For now, asking for one sentence is plenty.

## 5. The first verification runs automatically

Approve the plan review and **the first verification starts right away.** A real browser opens and starts clicking through your screens one by one, just as the test describes — exactly as a person would fill out a signup form and press a button.

While it runs, the screen shows **verifying**. A verification costs a tiny amount of credit, in proportion to how long it actually took. Each run costs so little that you can verify many times over with the credits you got at signup. (To start a verification, your balance needs to be at least 1 credit.)

Feel free to do other things while it runs. The result appears automatically when it finishes. Later, when you've fixed some code and want to check again, you can press the **Run test** button on the same test to re-run it anytime.

## 6. Read the result

When verification finishes, the result comes in just two colors.

- **Green = pass.** It worked the way your test described.
- **Red = fail.** Somewhere along the way, it didn't behave as expected.

A **video and screenshots** are saved with the result. You can see with your own eyes how the AI clicked through the screens and where it stopped. Even without reading code, "ah, this is where it broke" is plain to see.

If it failed, a **fix report** is created alongside. The report lays out where it stopped, why, and how to fix it. For example:

> Failed step: Cancel payment — the button isn't responding.
> Cause: the confirmation dialog never opened, so the flow stopped.
> Suggestion: check the handler wired to the cancel button.

Paste this report into an AI coding tool like Cursor or Claude Code, and the fix begins right away. Specnote doesn't edit the code itself. Instead, it clearly lays out what went wrong and why, then hands the fixing over to your AI tool.

## Next steps

Once you've run your first verification, you've got the basic flow down. Go deeper with these.

- The order a test gets made in, in more detail → [Creating tests](/en/docs/creating-scenarios)
- Running verifications and reading results in detail → [Running and results](/en/docs/running-and-results)
- Connecting your code for more accuracy → [Connect your code](/en/docs/connect-your-code)
- How credits and plans work → [Credits and plans](/en/docs/billing-and-credits)

By the way, if you connect your GitHub repository, Specnote pulls in your latest code on its own whenever the code changes, keeping tests more accurate. Connecting your code is optional — so we recommend experiencing a verification with one light test first.

---

Source: https://specnote.io/en/docs/quickstart