Account
Account, access and your data
Everything about your Serpel account lives under Settings: profile and sign-in, API tokens, apps you connected over OAuth, integrations and billing. Access to a project is set per project with three roles. You can export your data as JSON at any time and delete the account yourself.

Where do you manage your account?
Open Settings in the dashboard. Each tab covers one topic:
| Tab | What you do there | Guide |
|---|---|---|
| Profile and password | Change name, email address and password, link or unlink Google, export your data, delete the account. | This page |
| Integrations | Connect Google, Bing, PostHog and Plausible once for all projects, plus Slack and Discord notifications. | Search data, Web analytics |
| Billing | Plan, balance, top-ups, promo codes, agent spending, transactions and cancellation. | Credits and billing |
| Usage | Credits used in the last 30 days by feature, by project and by day. | Credits and billing |
| API tokens | Create and revoke tokens for the CLI, scripts and the REST API. | This page, REST API |
| API | The REST API address, the MCP server and the apps you connected through browser sign-in. | MCP for Claude Code |
| CLI | The sign-in command and example commands. Installation is in the CLI reference. | CLI reference |
| Crawler info | The user agent of SerpelBot and a link to its public information page. | SerpelBot |
How do you change your profile and password?
- Profile: your name and email address. Serpel uses them for sign-in and in reports.
- Password: at least 12 characters. When you change it, every other session is signed out.
- Sign-in methods: sign in with Google using the email address of your account, and Google is linked automatically. You can unlink it once the account has a password, and then sign in with email address and password.
- Accounts created with Google have no password at first. To set one, confirm it is you with a fresh Google sign-in, or let Serpel email you a link.
From the command line, serpel auth profile changes name and email address. It needs a token with full access and no project restriction, which is what the device login of serpel auth login creates by default.
How do API tokens work?
An API token starts with vsk_ and gives the CLI and the REST API access to your account. Create one under Settings → API tokens with the Token button. The dialog asks for:
- Name: something that tells you later where the token is used, for example “CLI on laptop”.
- Permissions: all 18 scopes are selected by default. Untick everything the token doesn’t need. The REST API reference lists each scope.
- Projects: “All my projects” or a single project. A token for one project gets HTTP 404 for every other project.
- Expiry: never, 30 days, 90 days or 1 year.
The token is shown exactly once. Serpel stores only a hash, so copy it right away. Managing tokens from the CLI or the API needs a token with full access, as the device login creates it. Through the CLI or the API you can also restrict a token to up to 100 projects and pick any expiry from 1 to 365 days. A revoked token stops working immediately.
serpel tokens create --name "Nightly crawl" --scope audit:write --scope audit:read --expires-in-days 90
serpel tokens list
serpel tokens revoke <id> --yesAPI token
- For the CLI, scripts, CI jobs and the REST API.
- You choose scopes, projects and expiry.
- Revoke it under Settings → API tokens.
Connected app
- For MCP clients such as Claude Code, Cursor and Codex.
- Access tokens last 1 hour, refresh tokens 30 days. The REST API rejects them.
- Disconnect it under Settings → API → Connected apps.
Who can access a project?
Access is set per project, not per account. Whoever creates a project is its owner and pays for its checks from their workspace. Other people can be added as viewer or editor:
Viewer
- Sees all data of the project.
- Can’t change settings or start checks.
Editor
- Everything a viewer can do.
- Changes settings, keywords and prompts and starts checks.
Owner
- Everything an editor can do.
- Removes members and deletes the project.
During the beta, only the Serpel team can add members to a project, and only people who already have an activated Serpel account. The projects guide covers the roles and project settings in detail.
How do you export your data?
Under Settings → Profile and password → Data and account, Export account data has a Download JSON button. The file holds your profile, workspace, projects, integrations and links to the project exports. Credentials are not included. The export is only available in the dashboard, an API token gets HTTP 403.
Issues, keywords, rankings and tasks of a project export as CSV or JSON, as described in history and exports.
How do you delete your account?
Confirm
Click Delete account and enter your password, or confirm with Google if you have no password.
Access ends
You are signed out. Sessions and integrations end at once.
immediatelyData is removed
Projects, crawls, keywords, reports and integrations are permanently removed after 30 days.
30 days
The deletion also closes your customer record at Stripe, which ends a running subscription, and revokes Serpel’s access to a connected Google account. The credit ledger and payment records stay for accounting, without your name or projects. Export your data first if you want to keep it.
Where to go next
Updated 5 Nov 2026
See also
- Credits and billingHow Serpel credits work: what each check costs, what stays free, how plans, monthly credits, top-ups, promo codes and cancellation work.
- Projects: set up and manage a website in SerpelCreate a project in Serpel, set its market, crawl, rank check and monitoring options, manage members and delete it. Plan limits explained.
- Serpel REST API referenceReference for the Serpel REST API: authentication, scopes, rate limits, errors, credits and every endpoint, with curl examples for crawls and rankings.
- Serpel CLI referenceReference for the serpel command line: install, sign-in, every command group, JSON output, exit codes and a GitHub Actions example.