Everything on one key: heartbeats, schedules, locks, configs and counters. Nothing here can change anything, and it needs a key that cannot either.
You need a key with scope: read. Signup gives you a write key; this makes the other kind:
curl -X POST https://pulse.nano-api.com/v1/keys \
-H "Authorization: Bearer $NANO_API_KEY" \
-H 'content-type: application/json' \
-d '{"name":"dashboard","scope":"read"}'
The scope is fixed at creation and a read key cannot issue a wider one, so this
is the one that is safe to keep in a browser. It is held in
sessionStorage and is gone when you close the tab.