# Account quickstart

Accounts are open for testing. Production collection, payments and MCP connections are not open. A working account or newly created API key does not enable those features. [Release status](/status/) describes feature availability, not live service health.

## 1. Choose a task

Explore the [Job Scraper API sample](/apis/job-scraper/) without signing in. Its records are examples, not live results for your input. Open the sample in the workspace to prepare your request; this does not execute a collection or spend credits.

## 2. Sign in

Use [Create an account](/signup/) or [Sign in](/login/). Google, GitHub and email-link sign-in are available. Continue with the method you used for your existing account. Do not assume that choosing another provider with the same email will merge identities or saved requests.

If a provider refuses the sign-in or you cancel it, return to the original tab and try again. If a method is temporarily unavailable, that is an account-service problem, not evidence that API execution has launched or that your account was deleted.

### Email links and expired sessions

- Request a fresh link if the email link has expired or already been used. Use the newest message and never send the link to support.
- If the link opens in another tab, finish sign-in there, then return to the original request tab and reload it. The temporary draft belongs to that original tab; it is not automatically copied into the email tab or another device.
- If your session expires while working, sign in again in the same tab to resume. Review the restored input before saving it; signing in does not run the task.
- If the original tab was closed, its temporary draft may be gone. Reopen a request you explicitly saved to your account or start from the product example.

## 3. Keep and reuse a request

The workspace can restore a validated temporary request draft in the same tab across reloads and sign-in redirects, while that draft remains valid. This is different from an account-saved request. Use **Save** when you want a configuration to remain in your account, and find it again under **Saved**.

Drafts contain allowed request settings, not API keys or sign-in tokens. Do not put secrets into query text. Review the inputs after returning from sign-in or opening a saved request. Reopening a request does not submit it for execution.

## 4. Understand what your workspace can do

| Available now | Not open yet |
| --- | --- |
| Profile, sessions and account settings | Live collection and task execution |
| Save and reopen request configurations | Credit purchases and paid usage |
| Create and revoke API keys | REST operation calls and MCP connections |

Key permissions and monthly credit limits are saved settings for future execution; they do not enable calls while execution is closed. A key's full value is shown only when created. Store it securely; do not put it in a URL, a saved request, screenshots or support messages. The future execution contract is documented separately in [API conventions](/docs/conventions/).

No trial balance or production result is promised by creating an account. Local demo balances and responses, when explicitly labeled as a demo, are sample data.

## If something goes wrong

Wait for account data to finish loading before interpreting an empty list or balance. A loading failure is not a confirmed zero balance. Use the displayed retry action for a failed read; do not repeatedly create keys or saved requests after an uncertain submission.

For help, send the safe error code, HTTP status and request identifier when provided, plus the page and action. Never include a key, email sign-in link or session token. [Contact support](/contact/) or return to the [sample walkthrough](/docs/quickstart/).


## Export or request deletion

In **Settings → Security**, export your account information before requesting deletion. The export includes your profile, saved configurations, available job and transaction records, credit orders and refunds, notification preferences and API key metadata. It also includes your sign-in provider identifiers, stored session details and connected-client consent records. Session details may include browser information, IP addresses and timestamps, so keep the downloaded file private. Full key values, key hashes, session tokens and provider credentials are excluded.

Confirming deletion immediately disables account access and revokes keys, connected client tokens and sign-in sessions. You cannot sign in again while deletion is pending. Permanent data cleanup is reviewed separately; records required for accounting, security or legal obligations may be retained. The confirmation is not a promise that every record has already been erased. Contact support if cleanup fails or you need help with a pending request.