Sign in
Paste your pck_… Cloud API key. The dashboard stores it locally in your
browser (localStorage) and uses it to fetch your account info. Nothing leaves
your machine until you choose to call the API.
Don't have a key yet? Email hello@prompty.khalo.org for an invited-tester key, or read the project on GitHub.
Overview
—
Usage this cycle
| Resource | Used | Quota | % |
|---|---|---|---|
| LLM calls | — | — | — |
| STT calls | — | — | — |
| Audio seconds transcribed | — | — | — |
Numbers reset at the start of the next 30-day cycle. Heavy users: consider pro or team tier (see Settings) for higher caps.
Audit log
Every proxied call your pck_ key has made this cycle. Metadata only —
provider, model, token counts, latency, status. We never log the transcript, the
rewrite, or the audio.
| Time | Endpoint | Provider | Model | In | Out | Latency | Status |
|---|---|---|---|---|---|---|---|
| Loading… | |||||||
API key
Your active Cloud API key (pck_…). The full token only lives in your browser
and the OSS-side prompty CLI keychain — the server only stores its SHA-256 hash.
Rotate key
Issue a fresh key and revoke the current one. Use if you suspect the current key has been exposed (a teammate saw your screen, you committed it to a public repo, etc.).
After rotation the dashboard's stored key updates automatically. You'll need to
prompty cloud login --key <new-key> on any machine using the old one.
Settings
Plan
You're on —. Quotas:
- trial — 10,000 LLM calls + 5,000 STT calls + 36,000 audio seconds / cycle
- pro — 50,000 LLM calls + 25,000 STT calls + 180,000 audio seconds / cycle
- team — 250,000 LLM calls + 125,000 STT calls + 900,000 audio seconds / cycle
Billing is intentionally not enabled yet — Cloud tier ships in invited-tester mode while we validate functionality. To switch tiers, email hello@prompty.khalo.org.
Backend URL
Pointing at: —
Default: https://api.prompty.khalo.org/v1. Change at sign-in if you're running
a local wrangler dev.
Privacy
This dashboard never sees your transcripts, audio, or rewrites — those go straight from
your prompty daemon to api.prompty.khalo.org and stop there. The
audit log behind Usage stores metadata only (provider, model, token counts,
latency) — see
THREAT-MODEL.md.
Couldn't reach the cloud
—