Keys go in headers, never in URLs
git log -p -S "?key=" --all | grep -n "key= " | headgrep -rnE "( api_?key| token)= [A-Za-z0-9_-]{16, }" logs/ *. db 2>/ dev/ null | head
Get the free fixes for code AI gets wrong
Each one shows what the AI wrote, what it should have written, and how to check your own app
What is going on
A URL is not a private channel. It is written to the server log, the CDN log, the browser history, the error tracker's breadcrumbs, and anything that stores "the request" for debugging. A header is not. The provider's own header exists for exactly this reason.
Where it bit
The lead-gen auditor called Gemini with the key as ?key= because that is the shortest way to make the call work, and the model wrote it that way. Failed calls logged the full URL into the local database. 54 rows held the live key. The same key was shared with a second tool, so scrubbing the rows did not un-leak anything. Rotated same day.
The practice
Key in the x-goog-api-key or Authorization: Bearer header. A scrub_secrets() pass on anything that gets logged. A regression test that fails if a key pattern ever appears in a URL again. Tests went from 27 to 44.
Get this check as a script you can run tonight

Make your coding agent prove it didn't cheat
Coding agents special-case, skip or edit tests so the check goes green. A five-sentence prompt Anthropic tested took Claude Opus 4 from cheating in 47% of runs to 5%- 3 min read
How to pick who fixes your vibe-coded app
Your app was built fast with AI and now something is wrong. Here is who can fix it, what they should do before they quote, the questions to ask and the red flags to walk away from - 3 min read
What an app check covers
An app check is an engineer reading the app your AI tools wrote, ranking what will break and writing the fix for each problem. Here is every area it covers, how the five days run and what you keep at the end
If this check came back with more than you expected, that is worth a conversation