AI fix: no provider
type | https://docs.frem.sh/reference/api/errors/autofix-no-provider |
| HTTP status | 409 Conflict |
What it means
Returned by POST /orgs/{org}/code-security/sast/findings/{id}/autofix (AI fixes for SAST findings). No fix was requested and no AI model was called.
Since 2026-10-14 the same refusal is answered with the type ai-fix-no-provider from POST /orgs/{org}/code-security/sast/findings/{id}/ai-fix. The paths above are deprecated and keep answering autofix-no-provider until 2027-10-15. Branch on either type.
Example detail message returned with this error:
- AI fixes need the organisation’s own model provider (bring your own key) under AI integrations. fremforge holds no key of its own.
The response also carries "reason": "no_provider".
What to do
Add a provider under AI integrations and make sure the autofix feature is not switched off there.
Response shape
All fremforge API errors are RFC 9457 problem+json:
{
"type": "https://docs.frem.sh/reference/api/errors/autofix-no-provider",
"title": "Conflict",
"status": 409,
"detail": "...",
"reason": "no_provider"
}Branch on type, not on title or detail - those are human-readable and may be reworded.