#7808: docs(venice): remove incorrect vapi_ prefix requirement

## Summary The Venice AI provider docs incorrectly claim that API keys have the format `vapi_xxxxxxxxxxxx`. This is not accurate - Venice API keys can have various prefixes (e.g., `QYE_...`) and Venice's official documentation does not specify any required prefix. ## Changes - Removed claims that Venice keys must start with `vapi_` - Changed example keys from `vapi_xxxxxxxxxxxx` to generic `your_api_key_here` - Updated troubleshooting section to remove the incorrect prefix check ## Files Changed - `docs/providers/venice.md` ## Testing N/A - documentation only change. <!-- greptile_comment --> <h2>Greptile Overview</h2> <h3>Greptile Summary</h3> Updates the Venice provider documentation to remove an incorrect assumption that API keys must start with a `vapi_` prefix. Examples are made prefix-agnostic (e.g., `your_api_key_here`), and the troubleshooting guidance is adjusted accordingly, so users don’t mistakenly reject valid Venice keys with other prefixes. <h3>Confidence Score: 5/5</h3> - This PR is safe to merge; it’s a small, self-contained documentation correction. - Only updates a single markdown doc to remove an incorrect key-prefix requirement and adjust examples; no code paths or behavior are affected. - No files require special attention <!-- greptile_other_comments_section --> **Context used:** - Context from `dashboard` - CLAUDE.md ([source](https://app.greptile.com/review/custom-context?memory=fd949e91-5c3a-4ab5-90a1-cbe184fd6ce8)) - Context from `dashboard` - AGENTS.md ([source](https://app.greptile.com/review/custom-context?memory=0d0c8278-ef8e-4d6c-ab21-f5527e322f13)) <!-- /greptile_comment -->