Account quickstart
Accounts and Job Search API are available. Credit purchases are available in Billing. MCP connections are not open yet. Use the Playground to check a price and run a collection, or follow the REST quickstart.
1. Choose a task
Section titled “1. Choose a task”Explore the Job Search API sample without signing in. It displays selected metadata from a labelled, verified capture, not live results for your input. Open the Playground to prepare your own request; this does not execute a collection or spend credits.
2. Sign in
Section titled “2. Sign in”Use Create an account or Sign in. Google, GitHub, Microsoft 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
Section titled “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 workspace. Reloading, leaving the Playground or signing in through a redirect discards unsaved input; sign-in does not restore it.
- If your session expires, sign in again and open a configuration you explicitly saved under Saved, or re-enter the input. Signing in does not run a task.
- If the original tab was closed, its unsaved input is gone. Reopen a saved configuration or start from the product example.
3. Keep and reuse a request
Section titled “3. Keep and reuse a request”Unsaved Playground input stays only in memory. Refreshing or leaving the page discards it; the Playground warns before leaving with unsaved edits. Get an estimate, then choose Save as new to keep the configuration in your account. Find it again under Saved and explicitly open it in the Playground. To replace the configuration you opened, choose Update original after reviewing the changes.
Saved configurations contain request settings, not API keys or sign-in tokens. Do not put secrets into query text. Review the current saved input and obtain a fresh estimate before running it. Reopening or saving a configuration does not submit a task for execution.
4. Understand what your workspace can do
Section titled “4. Understand what your workspace can do”| Available now | Not open yet |
|---|---|
| Profile, sessions, account settings and credit purchases | Notification delivery when the service is disabled |
| Save and reopen requests; run Job Search | Other planned APIs |
| Create API keys; call Job Search through REST | MCP connections |
Key permissions and monthly credit limits apply to task execution. 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 execution contract is documented separately in API conventions.
Eligible verified accounts receive 1,000 welcome credits once. Temporary email domains and previously claimed email or browser identities are ineligible. Signing in does not submit a task or guarantee matching results.
Review a completed task
Section titled “Review a completed task”In Tasks, review the sources, creation time, delivered records and credits charged. Open a task to inspect its frozen input and price, source outcomes, reservation, final charge and released credits. Open its results to inspect records or download a file before the displayed expiry. Empty, failed and expired results remain distinct.
For a new run, open the configuration in the Playground and review a fresh estimate. If a submission response is uncertain, recover its original command before starting another run. A new intended run uses a new canonical command key; changing the key is not a retry. See command recovery.
Request history
Section titled “Request history”Developer → Requests lists recent authenticated API request metadata. Use request identifiers, operation, HTTP status, duration and stable reason codes to investigate a problem. Request inputs and credentials are not retained in these diagnostics.
Metadata remains available for seven days. Logging is best effort: requests rejected before authentication and service outages can be missing. A successful download response does not prove that the entire file reached the client. History is separate from task outcomes and billing; use Tasks for results and Billing for charges. Account exports include the retained request metadata.
If something goes wrong
Section titled “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 or return to the sample walkthrough.
Email preferences
Section titled “Email preferences”Review Settings → Notifications for the current availability and your preferences. Saving a preference does not prove that an email was sent or delivered. When the service is disabled, saved preferences do not enable delivery. These preferences do not control sign-in emails.
Export or request deletion
Section titled “Export or request deletion”In Settings → Privacy, choose Request account export, follow the accepted request to its detail page, and download the export when it is ready. Export your information before requesting deletion. The JSON export includes your profile, saved configurations, task inputs and statuses, credit lots, reservations, ledger entries, credit orders and refund requests, notification preferences, API key metadata, and stored reward-program records. 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.
The download reads these stored records from one database snapshot. Fields ending in Units are exact integer strings: 1,000,000 units = 1 credit. Payment amountCents values use USD cents. Collected result files are not bundled; download them from each task before its result retention expires. Export downloads are limited to two starts per minute per account. A completed export status records server-side stream completion; it does not verify that the complete file reached your device. If a download fails, retry that existing export. If the export request itself is uncertain, recover its original command.
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.