Use the API · 1 of 5
API keys: live, test and their limits
Make keys for your code, give each only what it needs, and keep them from spending too much.
- Who can do this
- OwnersAdmins
- Reading time
- 1 min read
Keys are how your code talks to Navoras. Owners and admins make them on API keys; each belongs to the workspace and spends its credits.
Live and test keys
| Live (nv_live_…) | Test (nv_test_…) | |
|---|---|---|
| Speaks with | The real voices | Soft tones, one per word, timed like speech |
| Costs | Credits | Nothing |
| Good for | Your product | Wiring things up, and tests in CI |
Test keys go through the same text layer and give real-shaped timings, so you can check how KES 900 will be timed without spending anything.
Limits you can set
- Permissions: only the endpoints the key needs, such as
text_to_speechandvoices_read. - Monthly cap: the most credits the key may spend in a calendar month.
- Allowed addresses: the IP addresses or ranges it may be used from.
- Strict models: refuse model IDs from other providers rather than reading them as Navoras's.
- No logging: keep no text or audio from any of its requests.
Still stuck?
A person at Navoras reads every message and replies by email. Name your workspace, and the request ID if it's about one.