Developer Dashboard help
Availability: not available yet
The public Developer Dashboard has not been released. This page describes the verified P6-T6F preview.
What the preview shows
The English and Farsi Dashboard uses the signed-in browser session to load the organization, API-key metadata, and public model catalogue from the Platform API. Owners and Admins can create and revoke keys. Members can read models but cannot manage keys.
The approved DigiHoosh mark appears without a colored tile in the product navigation and browser tab. The organization avatar remains organization-specific and keeps its separate visual treatment.
Review usage
Owners and Admins can review organization usage; Members cannot access this section. The default filter covers the latest 30 UTC calendar dates. Choose inclusive From and Through dates, optionally select one public model, then choose Apply. Totals cover requests, input, output, total, cached-input, and reasoning tokens. The model breakdown has both a visual summary and an equivalent accessible table. Request history is newest first and loads up to 50 rows at a time.
Usage data contains public model and request identifiers only. Supplier cost is recorded privately for operational reconciliation, but it is not a customer price and is never exposed here. Provider routing, prompts, and responses also remain excluded.
Review API credit
Owners and Admins can review the active organization’s posted, reserved, and available API credit. Members receive no financial data. Amounts retain the Platform API’s exact twelve-decimal USD value in machine-readable markup; the visible amount uses USD minor units without calculating a balance in the browser. A positive amount below one cent is shown as Less than USD 0.01, never as zero.
The bounded history distinguishes promotional credit, pending usage reservations, final usage debits, refunded debits, and append-only refund reversals. Use Load more transactions to follow the opaque cursor. English shows Gregorian dates and Farsi shows Shamsi dates; each keeps the canonical UTC timestamp as accessible evidence. Wide screens use a semantic table and narrow screens use an equivalent list.
These are pre-tax operational credit records, not cash, payment, tax, invoice, settlement, revenue-recognition, or statutory-accounting records. Supplier cost, provider identity, margin, and other members’ data are never shown.
API-key safety
The Dashboard starts with no permissions selected and a 90-day expiration. The complete key is held only in component memory and shown until you confirm it was saved. If clipboard access fails, the value remains selectable for manual copying. It is never placed in browser storage, and later lists expose only safe metadata. Revocation requires explicit confirmation.
Where to go next
- See Get started for the overall product status.
- See Chat help for the end-user experience.
- See API overview for the planned API customer surface.
How long preview sign-in lasts
New customer sessions in the updated local preview stay signed in for up to seven days without active use. Returning and using the visible app renews that window, with a maximum of thirty days from sign-in. Leaving a tab open or background refreshes do not renew it. After either deadline, enter a new sign-in code; your saved conversations and account remain.
Closing/reopening the same normal browser profile or restarting the application does not itself sign you out. Sign out and authorized session revocation take effect immediately. Existing sessions keep their earlier deadline until you sign in again. Private browsing, clearing browser data or changing the website address can require a new login. This describes the local preview update, not a new public deployment.