tidbit
Docs/Getting started/Connect a provider credential

Connect a provider credential

3 min readUpdated July 2026

On the API path, Tidbit forwards each request on your own provider credential, supplied per request and stored nowhere. On the subscription paths (the Claude desktop app or Claude Code through the installer) there is no provider key to connect at all: your existing Claude sign-in keeps working, on your device.

Option A: provider API key#

Send your provider key on the x-tidbit-upstream-key header. The gateway forwards it per request and never writes it to disk. The BYOK installer (install-byok.sh, linked from the API setup steps) wires this up for Claude Code and the Anthropic SDK in one command.

Option B: OAuth bearer token#

Already hold an OAuth access token for the provider? Send it as Authorization: Bearer on each request instead of an API key. Same rule: forwarded, never stored.