Backup and restore, API keys, relay, and storage — the suite's controls, all in one
place. Every tool keeps its data in this browser's suite.* localStorage; the only
requests this page makes are the ones you press a button for — testing a key with its provider,
or testing the relay you configured.
One JSON snapshot of every suite.* key, values byte-for-byte —
settings, histories, caches, and your saved API keys, so treat the file like a password
and don't publish it. This is also the sanctioned bridge between the double-click
(file://) copy and a hosted copy: browsers give them separate storage, so export
on one side and import on the other.
Restore writes only suite.* keys, verbatim; anything else in the
file is skipped. Existing keys with the same names are overwritten.
Free personal keys for the tools that want one, stored as
suite.key.<name> on this machine only. Tools with a published demo tier work
without a key at shared low limits. Keys are masked here — and remember they ride along in
backups.
Walks the providers you're still missing, one at a time, and puts the details each signup form asks for one click from your clipboard. Every provider requires a captcha and its own terms, so the suite can never create an account for you — it opens the form, then takes the key you're given and checks it against the live API.
Your name and email are stored locally as
suite.profile.* purely to save retyping them into signup forms. They're never
sent anywhere by this page — but like everything else here they're included in a backup.
A tiny proxy you host yourself (template: relay/worker.js in the
repo) for the few sources that block browser scripts. Tools call it as
<base>?url=<encoded target>. Nothing in the suite requires it — unset,
every tool uses its built-in link-out or embedded-data path. Heads-up: the built
(dist) pages ship a Content-Security-Policy that only allows each tool's catalogued endpoints,
so a personal relay host is blocked there by design.
Keep several places and choose one active location for the weather, sky,
nature, and nearby tools. The active place is mirrored to suite.location so
every existing tool keeps working. Switching places resets only location-derived station,
state, and alert choices; coordinate-keyed and global caches remain available.
Everything the suite keeps in this browser. Deleting a key resets that bit of
state; cached API responses (suite.cache.*) are always safe to purge — tools
simply refetch.
| Key | Size | Value preview | Actions |
|---|