401 eror

[Serfinaaa100]

I have been trying for several days to connect RuFlo v3.57.0 to NoTrack using its OpenAI-compatible API.

My configuration:

• Operating system: Windows 10
• RuFlo version: 3.57.0
• Provider: OpenAI
• API endpoint: https://api.notrack.ai/v1
• Model: notrack-uncensored

The problem:

The API key works successfully when I send direct requests to NoTrack. Both /v1/models and /v1/chat/completions respond successfully.

However, RuFlo consistently returns this error:

Authentication failed (HTTP 401)

I have configured the provider and verified the endpoint and model, but I still cannot get even one agent working with NoTrack.

Could you please help me identify the cause and provide a working solution for Windows?

I would really appreciate your help. I have been blocked by this issue for several days.

I'm angry.........

[kamilkaczmareksolutions]

the Authentication failed (HTTP 401) message comes from the providers test command, and that check ignores your endpoint. for the openai provider it always calls https://api.openai.com/v1/models with your key (providers.ts in v3.57.0, where the 401 message is built). so your NoTrack key gets rejected by OpenAI, not by NoTrack. the baseUrl you set with providers configure -e is saved, but the test never reads it. it's the same in the latest 3.71.0

that means the 401 tells you nothing about whether NoTrack works with RuFlo. the useful question is whether an agent actually fails when it runs, or only providers test shows FAIL. if an agent fails too, please post the error it prints, since that would be a different code path

the test ignoring baseUrl for OpenAI-compatible endpoints is worth a separate issue, because anyone using a proxy or another OpenAI-compatible provider gets the same false 401

[Serfinaaa100]

Thank you for explaining this. That makes sense, and I understand now why the providers test command returns a false 401 error.

However, I still haven't been able to get an actual RuFlo agent working with NoTrack.

Could you please provide the exact commands and configuration steps to create and run a simple test agent using my custom OpenAI-compatible NoTrack endpoint?

My configuration is:

• Provider: OpenAI-compatible
• Base URL: https://api.notrack.ai/v1
• Model: notrack-uncensored
• RuFlo version: 3.57.0
• Operating system: Windows 10

I have already confirmed that my NoTrack API key works with direct requests to both /v1/models and /v1/chat/completions.

My goal is to use NoTrack as the actual LLM provider for all RuFlo agents, not just to pass the provider connectivity test.

I would really appreciate a working example or step-by-step instructions for Windows.

Thank you for your help!

[ruvnet]

@Serfinaaa100 What @kamilkaczmareksolutions found is right, and it still holds on current main: providers test for openai always calls https://api.openai.com/v1/models and ignores the endpoint you saved, so the 401 comes from OpenAI, not NoTrack.

There is a second gap: agent execution never reads the openai provider entry. agent_execute only dispatches to Anthropic, OpenRouter or Ollama (agent-execute-core.ts). The OpenRouter branch is a plain OpenAI-compatible client with a configurable base URL, so as a workaround set these in the env block of your Ruflo MCP server entry (or the shell you start Claude Code from):

RUFLO_PROVIDER=openrouter
OPENROUTER_API_KEY=<your NoTrack key>
OPENROUTER_BASE_URL=https://api.notrack.ai
OPENROUTER_DEFAULT_MODEL=notrack-uncensored

Leave /v1 off the base URL; Ruflo appends /v1/chat/completions. When you spawn agents from the CLI, pass the provider and model: agent spawn -t coder -p openrouter -m notrack-uncensored. That matters because a per-agent provider overrides RUFLO_PROVIDER and the CLI defaults it to anthropic, and tier aliases like sonnet are mapped to Anthropic model names.

This covers agent_execute only. Hive-mind and the background workers run the claude CLI and don't use these settings. Please also update to 3.71.4 (npx ruflo@latest). Both gaps are now tracked in #4834.

_{Automated answer from the ruflo maintainers' discussion triage - reply here if it doesn't solve it.}