FAQ & troubleshooting

Resolve common questions about availability, account access, data, and execution.

Why can I browse but not launch?

Public discovery is open. A private launch additionally needs sign-in, product approval, an available qualified runtime or enabled order mode, and the applicable billing checks. Read the action message in the workspace to identify the missing condition.

Submitting an early-access request starts manual review. It does not automatically create an account or grant access.

Why is my email request not shown on my account?

An anonymous request is not linked just because the same email is entered after sign-in. Complete the email verification link, sign in with Google or your durable wallet account, and explicitly confirm the association. Google sign-in alone does not claim a request with a matching email. Existing manual account associations remain supported.

Request received means the form was saved. Email delivery, email verification, review, invitation acceptance, and product permission are separate steps. Follow the state shown by the form or contact support if verification delivery is unavailable.

Early-access workflow — Review verification, account association, and product approval.

Can I call a chat-completions endpoint?

There is no hosted real-time chat-completions or streaming endpoint. For offline chat completions, the Batch API takes an OpenAI Batch JSONL file of /v1/chat/completions requests on a supported public Hugging Face model and returns an output file within the completion window you choose (24 to 168 hours). To serve a model interactively, use its own published artifacts and deployment instructions.

Batch API — Offline chat completions on your own JSONL file.

Why was my dataset rejected?

  • Confirm the file is UTF-8 JSONL and every non-empty line is valid JSON.
  • Choose instruction, preference, or corpus and use exactly that format’s fields.
  • Use non-empty string values, a simple .jsonl filename, and at most 5 MiB.
  • Keep the file between 1 and 10,000 non-empty rows. These limits are for the dataset library, not for Batch API files.
  • Confirm data rights and review active and retained library limits.

Dataset formats — Compare valid examples and upload limits.

Did a quote or failed request charge me?

Requesting a quote does not reserve credits. Explicit confirmation reserves the reviewed price after server checks. If confirmation timed out, reconcile the original idempotent request before submitting another action.

A delivered order can still have a held financial receipt. Check the receipt’s charged and released fields for settlement. Active cancellation may take time to drain and reconcile.

Recover access or ask for help

Sign in with the Google account or wallet already linked to the workspace. A temporary browser cookie is not an account recovery method, so link Google or a wallet while you still have access. Accounts with matching emails are never merged automatically.

For an API problem, keep the safe request reference, time, route, HTTP status, and error code. For a workspace problem, include the visible message and the steps that produced it. Keep keys and private dataset content out of shared diagnostics.

Support — Find the current help and contact information.

Errors & retries — Handle authentication, conflicts, limits, and outages.

Account & access — Review sign-in methods, sessions, and pilot access.