Set up a paid API key
Anthropic and OpenAI APIs are working last-resort model paths. chekd separates finding a key, authorizing it, testing it, selecting the provider, and approving spend so none of those steps silently grants the next one.
An API key found in your environment is not authorized, tested, selected, or spent just because it exists.
Bounded by design
The connection test makes a real provider request and reports its exact cost. Passing it does not authorize a later job: every paid job still needs its own exact dollar ceiling and final confirmation.
Connect in five deliberate steps
- Open Settings → AI & governance Choose Anthropic API or OpenAI API. chekd uses only the exact provider you select.
- Authorize one key source Authorize a detected environment key, paste a key for Use once, or choose Remember on device. Discovery alone never authorizes use.
- Choose the storage boundary Use once keeps the key in process memory only. Remember on device uses Windows Credential Manager, macOS Keychain, or Linux Secret Service when available (macOS/Linux support is beta); chekd settings keep only an opaque reference.
- Run the capped connection test The test uses the selected Balanced or Top Tier model, sends no screenshots, source, or tools, and shows the tested model and actual cost.
- Select the provider After the current effort profile passes, choose Use this provider. A later paid job still cannot run without that job’s separate ceiling and confirmation.
What stays local
Key values never enter browser storage, chekd settings, logs, exports, screenshots, or run artifacts. Provider requests leave directly from this device through the connection you authorize; returned usage and cost are tracked locally to enforce your ceiling. Prefer no provider bill or cloud egress? Use Ollama.