NVIDIA api does not work, during testing or pinging.

[Handyfff]

Manually typed the key.
Then went into the config file and edited it there too.

Does not work.

Error 403 on Testing. And AUTH FAIL on models.

Same key working in OpenCode.

[vava-nessa]

I couldn't reproduce the issue on my end (NVIDIA works fine here), so this looks like a local config issue.

Please try to regenerate your key at build.nvidia.com (https://build.nvidia.com)
make sure it's a NIM API key, not an NGC key

Test with curl:

curl -X POST https://integrate.api.nvidia.com/v1/chat/completions \
  -H "Authorization: Bearer YOUR_KEY" \
  -H "Content-Type: application/json" \
  -d '{"model":"meta/llama-3.1-8b-instruct","messages":[{"role":"user","content":"hi"}],"max_tokens":1}'

If curl works, try clearing ~/.free-coding-models.json and re-entering the key via Settings (P)

Let me know how it goes!

[lehneres]

Test the via curl is successful:

curl -X POST https://integrate.api.nvidia.com/v1/chat/completions \
  -H "Authorization: Bearer redacted" \
  -H "Content-Type: application/json" \
  -d '{"model":"meta/llama-3.1-8b-instruct","messages":[{"role":"user","content":"hi"}],"max_tokens":1}'

{"id":"chatcmpl-bf0393bf-a85e-4880-b26a-c56c0b05222c","choices":[{"index":0,"message":{"content":"How","role":"assistant","reasoning_content":null},"finish_reason":"length"}],"created":1779963149,"model":"meta/llama-3.1-8b-instruct","object":"chat.completion","usage":{"prompt_tokens":36,"completion_tokens":1,"total_tokens":37,"prompt_tokens_details":{"audio_tokens":null,"cached_tokens":32}},"nvext":{"worker_id":{"prefill_worker_id":7587894946598083103,"prefill_dp_rank":0,"decode_worker_id":7587894946598083103,"decode_dp_rank":0},"timing":{"request_received_ms":1779963149919,"prefill_wait_time_ms":0.78003,"prefill_time_ms":17.387689,"ttft_ms":18.167718999999998,"total_time_ms":18.193331999999998,"kv_hit_rate":0.3333333333333333,"router_queue_depth":0}}}% 

replaced key configured in free-coding-models.json but error in tool is still "NViDIA NIM rejected tech configured key with 403 [...]"