The same account you use on the site. The email form below is for the local emulator.
This console is for DataWorks staff. Your own account is on the site, under Account.
What the assistant's model calls cost, as every answered question is added up (the api's Search and the site's own chat land in the same daily total). Above the daily cap Search answers "paused until tomorrow" and charges nothing; the cap is DW_DAILY_SPEND_CAP_USD in the api's environment.
Every account as the product sheet sells it (decision 027). Click one for its detail: what it bought, its seats, its key, its ceilings, its audit.
What the account bought, as the product sheet sells it (decision 027). The ceilings (below) are the tier's brake against runaway scripts and are never shown to the customer.
Every seat in every account: who can sign in to the portal, connect an AI tool, or open a report. Seats are given and taken on the account's detail.
One per tier: the brake against a runaway script (a 429 for the rest of the day), never a quota and never shown to a customer. Seats here are the default; an account can carry its own.
Access requests from the Insights gate's form arrive at the inquiry address and are kept on the site (the site's request list, staff sign-in). Account inquiries come by email from the Build page. A queue here that turns a request into an account in two clicks is the next slice of this console.
The latest questions and calls, newest first, from the api's own records. A seat's question keeps who, when, how long and the cost, never its text; a free visitor's (a guest, or signed in on the free allowance) keeps the question and the answer, as the privacy page says, and a signed-in visitor's row names the address they signed in with. The turns of one conversation are shown together, in the order asked. Key and connector calls keep the endpoint or tool, never the values.
The data operations board: sources, schedules, runs and open items. It also has its own page at /ops.