Website account

Log in and view your balance, AI usage, activity heatmap, and recent transactions

Select Log in in the website navigation and choose an available GitHub or Google login option. The original login dialog displays an authorization code and opens an authorization window. After provider authentication, enter the code from the original dialog on the confirmation page. Once confirmed, the original page continues automatically and returns you to the page you were browsing.

If the authorization window does not open, allow pop-ups for the Downcity website and try again. You can cancel while waiting. If login expires or fails, choose a login option again to retry.

Once logged in, select your account name in the navigation and choose Account to view your name, email, and user ID. If your provider does not supply an email address, the page shows “Not provided”.

Balance and activity

The account center has a sidebar with Overview, Usage & activity, Transactions, API Keys, Request history, Models & setup, and Profile. On mobile, use the section menu at the top. The view URL parameter supports direct links; sections share loaded data, and refreshing preserves the current view.

The account center shows:

  • Available Credits, permanent Credits, and temporary Credits with expiration dates.
  • Month-to-date spend, AI request count, and metered Tokens.
  • A daily trend chart with separate Spend (USD), Tokens and Requests views for the last 7, 30 or 90 days. Hover for daily details; dates before coverage remain unknown.
  • An activity heatmap for the past 365 days, colored by AI requests. Hover or focus with the keyboard for details, click to pin a day, then close the details or press Escape to unpin.
  • The latest three transactions in Overview, and up to twenty in Transactions. Select a record to expand its description and status.

Daily statistics use your browser timezone. AI requests include failed or cancelled executions; Tokens include only measured usage. Spend comes from independent billing records and is not estimated from Tokens. Dates before data coverage are not treated as zero activity.

Credits added may come from purchases or grants. The website currently links to Credits information and does not provide a direct top-up flow. If a service is unavailable, the affected section shows an error. Select Refresh to try again.

API key management

Select API Keys in your account center, or open key management. View your own keys, create new ones, edit names, model / route permissions, expiration and spending soft limits, or disable, reactivate and permanently revoke keys.

Permission choices come from the service’s published language model and route catalog. Selecting all current and future entries also grants access to entries published later; selecting none blocks all inference. Access to a route does not grant direct access to its model. Previously granted entries that are no longer available remain in the editor and can be removed. If the catalog is unavailable, existing permissions are preserved; refresh it before changing permissions or creating a key.

Enter spending limits in whole Credits. Blank means no limit; zero blocks new calls. The limit checks successfully settled lifetime spending for that key. Editing the limit does not reset spending. No funds are reserved: concurrent in-flight requests can exceed the limit, and all keys share your account balance. Enter expiration in your browser’s local time, or leave it blank for no automatic expiration.

The complete key is shown only once after creation. Copy and store it securely. Closing the dialog, leaving the Keys section or signing out removes it from the page; it cannot be retrieved again. If clipboard access is unavailable, select the text and copy manually. If creation is interrupted, refresh the list to check the result first. Revoke any newly created key whose secret you did not receive before creating another.

Disabled keys can be reactivated. Revocation is permanent; check the name and prefix before confirming. Disabling, revoking or expiration blocks new calls, while in-flight calls still settle. A key grants only permitted inference access and cannot sign you in or manage your account. See the model relay guide for OpenAI client configuration.

Request history

Open Request history to view your own relay requests, with up to 20 records per page, filtering by key, previous/older pages, and refresh-latest controls. Key names and prefixes come from your own key list. If unavailable, records show key IDs; signed-in calls are identified separately.

Each record shows the requested public model / route, execution state, input/output tokens, settled Credits, duration and settlement state. Unknown / not provided does not mean zero. Input tokens are summed only when both cached and uncached input are known; reasoning tokens are part of output and are not added again. Pending, failed or missing charges are not presented as free. Select Details & attempts for request ID, resolved public model, metering breakdown and safe upstream attempt metadata: channel ID, actual upstream model, HTTP status and first-content latency. No prompts, answers or provider credentials are displayed.

Only key filtering is available; backend date, state and model filters are not provided. Requests rejected before execution may have no record. Interrupted requests may remain running, so consult metering and settlement separately.

Models and setup

Models & setup reads the live public language model and route catalog, with search by name or ID. It preserves backend context windows, reasoning efforts and structured pricing, including currency, units, scale and conditions. Missing fields are marked as unavailable. Tools or vision support is not inferred from tags, and prices are not converted into Credits.

The OpenAI Base URL comes from the website server’s Federation connection configuration. Choose an entry and protocol to copy a curl example for OpenAI Chat Completions or the native Downcity model stream. Examples use only YOUR_DOWNCITY_API_KEY; the page never reads or saves a real key. Replace the placeholder in your secure client. Native streaming uses its own Downcity SSE events. Responses and Anthropic Messages are not supported.

Catalog visibility does not grant a calling key permission: authorize the entry in key management. Catalog failures provide retry controls, and any retained older catalog is explicitly identified.

Select Log out to revoke the current website login and end the session in this browser. If logout fails, retry when the service is available. Log in again when your session expires. Logging out of the website does not log you out of the desktop app or other devices.