Bring Your Own Keys — setup guide
BYOK mode lets voxspek call your chosen AI providers and GitHub directly from your browser using your own API keys. Unlimited issues, no subscription, you pay the providers directly at cost. Pick an audio provider (OpenAI or Groq) and a summary provider (Anthropic or OpenAI), then grab the API keys below.
Anthropic API Key
Claude Haiku 4.5 powers the AI that structures your voice memo into a proper GitHub issue.
- Go to console.anthropic.com/settings/keys and sign in (or create an account).
-
Click Create Key. Name it something like
voxspek. -
Copy the key that appears — it starts with
sk-ant-api03-. This is the only time you'll see it. If you lose it, you'll need to create a new one. - Paste it into voxspek Settings → Plan → Bring Your Own Keys → Anthropic API Key, then click Test.
OpenAI API Key
Whisper transcribes your voice recording into text before Claude structures it.
- Go to platform.openai.com/api-keys and sign in (or create an account).
-
Click Create new secret key. Name it something like
voxspek, leave the project as default, grant it All permissions (or at minimummodel.requestfor audio). -
Copy the key — starts with
sk-proj-for project keys orsk-for legacy keys. Only shown once. - Paste it into voxspek Settings → Plan → Bring Your Own Keys → OpenAI API Key, then click Test.
Groq API Key
Groq runs Whisper Large v3 Turbo for fast, free-tier audio transcription. An alternative to OpenAI for the audio step.
- Go to console.groq.com/keys and sign in (or create an account — free, no credit card required).
-
Click Create API Key. Name it something like
voxspek. -
Copy the key — it starts with
gsk_. Only shown once. - In voxspek Settings → Plan → BYOK, select Groq Whisper as your audio provider, then paste the key and click Test.
Google AI API Key
Gemini 2.0 Flash handles both audio transcription and issue structuring. One key, two capabilities — the cheapest option.
- Go to aistudio.google.com/apikey and sign in with your Google account.
- Click Create API Key. Select any Google Cloud project (or let it create one for you).
-
Copy the key — it starts with
AIza. Only shown once. - In voxspek Settings → Plan → BYOK, select Google Gemini 2.0 Flash as your audio and/or summary provider, then paste the key and click Test.
GitHub Personal Access Token
Used to file the structured issue into your repo under your own GitHub identity. Required in every mode — Trial, BYOK, and Managed Pro.
- Go to github.com/settings/personal-access-tokens/new (Settings → Developer settings → Personal access tokens → Fine-grained tokens).
-
Token name:
voxspek.
Expiration: pick whatever fits your risk tolerance (90 days is a safe default, up to 1 year).
Repository access: Only select repositories → pick every repo you want to file bugs into. - Repository permissions: scroll to Issues and set it to Read and write. That’s the only permission you need. Everything else can stay at "No access".
-
Click Generate token at the bottom. Copy the token — starts with
github_pat_. Only shown once. - Paste it into voxspek Settings → GitHub → Personal Access Token, then click Test.
Troubleshooting
Anthropic test returns "Invalid key"
Double-check you copied the entire key including the sk-ant-api03- prefix. If it still fails, go back to the Anthropic console and confirm the key is listed as active. Disabled or deleted keys will not authenticate.
Groq test returns "Invalid key"
Make sure the key starts with gsk_ and was copied in full. Go to the Groq console and verify the key is listed as active. If it was revoked, create a new one.
OpenAI test returns "Insufficient quota"
You have a valid key but haven't added funds. Go to platform.openai.com/settings/organization/billing, add a payment method, and purchase prepaid credits ($5 minimum). Retry the test after the purchase completes.
GitHub test returns "Resource not accessible by personal access token"
Your PAT is missing Issues: Read and write on the target repo. Generate a new token at the PATs page, make sure to select the correct repos under "Repository access" and grant "Issues: Read and write" under Repository permissions.
Test button spins forever
Usually a network issue or a CORS block from a browser extension blocking third-party API calls (uBlock Origin, Privacy Badger, etc.). Temporarily disable content blockers for api.anthropic.com, api.openai.com, and api.github.com and retry.
My key works in curl but not in the extension
Chrome extensions have strict CORS rules. voxspek declares host permissions for all three providers in its manifest, so direct calls should work out of the box. If they don't, check that you're on the latest version of the extension (chrome://extensions → refresh) and that no corporate proxy is intercepting traffic.
How much will this actually cost me?
Per issue: roughly $0.003 (Claude Haiku for triage) + $0.003 (Whisper for a typical 30-second recording) = ~$0.006 per issue. That's 166 issues for a dollar. If you're filing 20 bugs a day, that's ~$3.60/month in provider fees. Managed Pro ($9/mo) makes sense above ~1,500 issues/mo; BYOK wins below that.