Uncensored AI for vulnerability research
Read the patch, find the gap, write the note
Patch diffing is looking at the thing the vendor did not want you to find. A model that will not talk about the old function is not helping you decide whether the fix is real.
Why the mainstream APIs fail here
Asking "what did this patch miss" is treated as a request to exploit the product. You are reading a public diff or a build you own. The refusal hides the interesting function.
How Wild West API is used for this
Paste the diff, the old function, the new function. Ask what still trusts the caller. Draft the vendor note. Do not send the exploit to a third-party host; send it to the tracker the programme named.
A working loop
- Work on in-scope or owned builds only.
- Prompt with the diff, not with a request to attack customers.
- Use a key per research stream so spend is visible.
Details are on the privacy page. Per-model prices are on /models and the pricing model is on /pricing.