Getting started & API keys
Access to the Kuno API uses personal, read-only API keys created right in the Kuno app. Here's how to get to your first request in five minutes.
Create an API key
In the Kuno app, open Settings → Developer → API keys and tap Create new key. You give it a label, pick the scopes and optionally an expiry date.
The key is shown exactly once. Kuno only stores a hash. Copy it straight into your password manager — afterwards it can't be retrieved, only rotated.
Keys use the format kuno_live_… and are personal: they see exactly the
recordings you see in the app — never anyone else's.
Scopes
| Scope | Access |
|---|---|
| recordings.read | List recordings and fetch metadata (title, status, date). |
| summaries.read | Read note content: summary, transcript, key points. |
| actions.read | List action items across all your recordings. |
All scopes are read-only — writing, changing or deleting through the API is deliberately not possible.
First request
Authenticate with a Bearer token in the Authorization header:
curl https://api.heykuno.com/v1/recordings?limit=5 \
-H "Authorization: Bearer kuno_live_your_key"The response is JSON with your latest recordings. All endpoints are in the REST API reference; for AI assistants like Claude or Cursor, the MCP server is the easier route.
Rotate or revoke a key
In Settings → Developer → API keys you can rotate any key (the old key becomes invalid, you immediately get a new one) or revoke it (immediately invalid). A leaked key is out of circulation in seconds.