The dashboard

Pick your provider to see whether your org has an API key and that provider’s key yet, and the two ways to connect a LiveKit agent, ready to copy: our plugin, or the provider’s own plugin with the changed lines marked. They are the snippets on Sarvam, Raya and ElevenLabs with LiveKit.

• The hit rate, and the characters kept off your provider’s bill, over the last 24 hours or the last 7, 30 or 90 days.
• A column per hour or per day, cached under synthesized, and the same split per provider.
• Hours are shown in your time zone and days are UTC days. Counts arrive within about a minute. A sentence counts once the provider has finished it, including one that finished after your agent was interrupted; a failed one doesn’t count.
• On the drop-in endpoints that cache whole requests (REST and HTTP stream), each request counts as one sentence.

• The balance, and about how many characters served from the cache it covers.
• Writers and admins buy credit packs here, paid through Dodo Payments; the credit appears within seconds. Readers see the balance and history.
• The history lists the free credit, every purchase and refund, and usage summed per UTC day.
• Below $1 every dashboard page warns you; at zero, new connections are refused until you buy more.

Prices, refunds and what happens at zero are in Pricing and billing.

• Create a key and name it after where it’s used. It’s shown once: copy it into your agent’s secrets.
• The list shows each key’s name, its first characters and when it was created.
• Deleting a key stops it within a few seconds, including on connections already open. Your cache stays.

More in Authentication.

• Set, replace or delete one key per provider. A change is used within a few seconds.
• Keys are stored encrypted and never shown again, only their last four characters.
• Saving doesn’t check a key with the provider: a wrong one surfaces as the provider’s refusal on your first request. Without a key, that provider’s requests fail with provider_key_missing.

The same actions are in the REST API, with an API key.

• Reader sees every page and changes nothing. Writer also creates and deletes API keys, sets provider keys, changes settings and buys credit. Admin also invites and removes members and sets their roles. You are the admin of the org you get at sign-up.
• Admins invite by email with a role. Someone who already has an account joins right away; anyone else joins the first time they sign in with that email, and gets an org of their own too. No email is sent, so tell them.
• Anyone can leave an org from their own row. An org always keeps an admin and a member: its only admin has to make someone else an admin before leaving or stepping down, and its last member can’t leave. Orgs are never deleted.
• API keys belong to the org, not to whoever created them: removing a member leaves their keys working.

• 365 days unless you change it: 1, 7, 30, 90 or 365 days, any whole number of days up to 3,650, or off.
• It counts from when the audio was cached; playing it doesn’t extend it. Audio is deleted within about a day after.
• A change applies to everything already cached: lowering it deletes older audio, raising it keeps audio longer.
• Off: nothing new is cached, and cached audio is deleted within about two days.

Settings also has your org’s name and its ID, which never changes. Only an org’s writers and admins can change its settings, create or delete API keys, and set or delete provider keys.

To delete your account, write to [email protected] from the address you sign in with: we erase your account, and every org where you are the only member, with its keys and cached audio. Orgs you share keep running without you. Delete your API keys first to stop all traffic at once.