AI_APICallError: Invalid JSON response

Describe the bug When configuring a Jina AI embedding endpoint via the "Custom / OpenAI-Compatible" provider option, Blinko fails to process embedding requests. Direct API calls to the same endpoint, with the same API key, model, and payload, succeed without issue — confirming the problem is in how Blinko constructs or parses the request/response, not with the third-party API itself. The error evolves depending on configuration:

With base URL https://api.jina.ai (no /v1): AI_APICallError: Not Found With base URL https://api.jina.ai/v1 (correct, matches OpenAI-compatible convention): AI_APICallError: Invalid JSON response

To Reproduce Steps to reproduce the behavior:

Go to Settings > AI > Embedding Select provider type "Custom" / "OpenAI-Compatible" Enter Base URL: https://api.jina.ai/v1 Enter Model: jina-embeddings-v3 Enter a valid Jina API key Set Dimensions: 1024 Click "Test Connection" — this reports success Enable knowledge base search and send a message in AI Chat See error: AI_APICallError: Invalid JSON response

Expected behavior The embedding request should succeed and return a valid vector, matching the behavior confirmed via a direct API call to the same endpoint: powershellInvoke-RestMethod -Uri "https://api.jina.ai/v1/embeddings" -Method Post -Headers @{ "Authorization" = "Bearer <redacted>" } -ContentType "application/json" ` -Body '{"input":["hello world"],"model":"jina-embeddings-v3","dimensions":1024}' This returns a valid response: model object usage data

---

jina-embeddings-v3 list @{total_tokens=5} {@{object=embedding; index=0; embedding=System.Object[]}} Screenshots N/A

Desktop (please complete the following information):

OS: Windows Browser: Chrome Version: latest

Additional context

"Test Connection" reports success even though the actual chat/embedding request fails — this appears to be a separate issue where Test Connection does not validate the same request path used during real usage. Also tested with base URL missing /v1, which produced a different error (Not Found), suggesting Blinko does append a path segment to the base URL, but something in the request or response handling breaks specifically with Jina's response shape once the path is correct. Jina's API key, model name, and endpoint were all independently verified working via direct PowerShell Invoke-RestMethod calls before and after each Blinko configuration change.