Less searching. More building.

Email verification is required before dashboard and API access. Open the email sent to your registered address. The one-time link expires in 15 minutes. A resend invalidates the previous link.

Sign in and request a new link from the verification page. Wait for the newest email and check your spam folder. Your account remains registered; you do not need to create another one.

Use Forgot password with the email you registered. Follow the single-use reset link and choose a new password. Support never needs your password or reset token.

Use the API Keys page to manage your keys. Revoke an exposed key and replace it in your server environment. Remove the exposed value from logs and public configuration too.

It describes the billing rule: credits are charged only for validated successful output. It does not promise that every target can be retrieved. Block pages, unresolved challenges, and empty results fail validation without a successful charge.

The job is still processing. Keep the returned job ID and poll GET /v1/jobs/:id until it reaches a terminal state. Repeatedly submitting the target can create extra jobs.

A requested capability is not enabled. Check GET /v1/capabilities or remove the unsupported option. Rejected unsupported options do not create a billable success.

External scraping adapters are currently simulated. Accounts, jobs, balances, and logs are persisted, but simulated success is not proof that a real target can be accessed.

Standard success costs 1 credit. Optional language extraction adds 2 and JavaScript rendering adds 3. A successful combined request costs 6. Failed output costs 0, and retries do not multiply the success charge.

Starter is $8 for 10,000 credits, Pro is $18 for 25,000, and Business is $60 for 100,000. Available packs and your current balance are shown on Billing.

No. The current checkout simulates payment events and updates the local account balance. Do not send cryptocurrency to test the MVP. Real merchant checkout has not been enabled.

Any language with an HTTP client can call the API. The toolkit includes runnable Python and JavaScript examples, a Postman collection, and an OpenAPI contract. cURL and Go examples are in the documentation.

Use its generic HTTP request step with your backend base URL, a target URL, and an X-API-Key secret header. Add polling for HTTP 202. This does not require or imply an official marketplace connector.

Include the request ID, approximate UTC time, HTTP status, and a redacted description. Never include your password, API key, session cookie, payment secret, or a target URL containing private credentials.