[BUG] Error - Invalid API endpoint. Please check your URL configuration

[denileo82]

Describe the bug
A clear and concise description of what the bug is.

To Reproduce
Steps to reproduce the behavior:

1. Go to '...'
2. Click on '....'
3. Scroll down to '....'
4. See error

Expected behavior
Expect to index my codebase in QDrant

Screenshots
If applicable, add screenshots to help explain your problem.

Video
Add a video of the incident happening, it will help us debug

What version of zoo are you running
3.64.0 (tested also pre-release version, same issue)

Additional context
after updating to new version I can't index any longer. Also tested with Local qdrant or cloud none is working

[CipherChaos]

Hey there! @denileo82

Thanks for reporting this issue.

Let’s work together to get this resolved. Here are a few quick things to check:

1. URL format: In v3.64.0, the endpoint format has become a bit stricter. Please try using:

# Local
QDRANT_URL=http://localhost:6333

# Cloud  
QDRANT_URL=https://your-cluster.qdrant.io:6333

remember, no trailing slashes or extra paths. Also QDRANT_HOST and QDRANT_PORT variables are abandoned(deprecated) in this version.

2. Environment variables: Please check that you’re using these names and there is no misspell or something:

QDRANT_URL=...
QDRANT_API_KEY=...  # only for cloud

3. Send Logs: Could you share the complete error log and your configuration (just remove any sensitive info)? That’ll help us figure out which endpoint is causing the issue.

If you need a quick fix, I recommend you to downgrade to v3.63.0 while we sort this out:

npm install @zoo-ai/zoo@3.63.0

Also, consider running with debug logging for more insights (or if you are using docker, please send docker logs):

DEBUG=qdrant:* your-command

[denileo82]

I've found the issue, it was not my qdrant. The error is not clear. Actually my openrouter was not allowing in the guardrails the embeeding model. I think you can use this ticket to improve the error message to indicate if the problem is Qdrant or the model provider Thanks 🙂

…

________________________________ De: Ariyan Bolandi ***@***.***> Enviado: quarta-feira, 1 de julho de 2026 12:08 Para: Zoo-Code-Org/Zoo-Code ***@***.***> Cc: Deni Leocadio ***@***.***>; Mention ***@***.***> Assunto: Re: [Zoo-Code-Org/Zoo-Code] [BUG] Error - Invalid API endpoint. Please check your URL configuration (Issue #773) [https://avatars.githubusercontent.com/u/185718123?s=20&v=4]CipherChaos left a comment (Zoo-Code-Org/Zoo-Code#773)<#773 (comment)> Hey there! @denileo82<https://github.com/denileo82> Thanks for reporting this issue. Let’s work together to get this resolved. Here are a few quick things to check: 1. URL format: In v3.64.0, the endpoint format has become a bit stricter. Please try using: # Local QDRANT_URL=http://localhost:6333 # Cloud QDRANT_URL=https://your-cluster.qdrant.io:6333 remember, no trailing slashes or extra paths. Also QDRANT_HOST and QDRANT_PORT variables are abandoned(deprecated) in this version. 2. Environment variables: Please check that you’re using these names and there is no misspell or something: QDRANT_URL=... QDRANT_API_KEY=... # only for cloud 3. Send Logs: Could you share the complete error log and your configuration (just remove any sensitive info)? That’ll help us figure out which endpoint is causing the issue. If you need a quick fix, I recommend you to downgrade to v3.63.0 while we sort this out: npm install @***@***.*** Also, consider running with debug logging for more insights (or if you are using docker, please send docker logs): DEBUG=qdrant:* your-command — Reply to this email directly, view it on GitHub<#773?email_source=notifications&email_token=AKARNU5YLLRPW2B3357MQXL5CUSO3A5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTIOBVGY3TENBVGA22M4TFMFZW63VHNVSW45DJN5XKKZLWMVXHJLDGN5XXIZLSL5RWY2LDNM#issuecomment-4856724505>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AKARNU2OKKTJM7A56GGXEF35CUSO3AVCNFSNUABGKJSXA33TNF2G64TZHMYTEMJZGQ3DQMRSGQ5US43TOVSTWNBXG44TINBUGA4DJILWAI>. You are receiving this because you were mentioned.Message ID: ***@***.***>