Problem Description
Currently, Nanobot's ollama provider is designed for local Ollama instances (no auth). Users can already access Ollama Cloud models by routing through a local Ollama instance, but this potentially adds unnecessary latency and requires running local infrastructure. There's no documented way to connect directly to Ollama's cloud API.
Ollama Cloud API Details
From Ollama's documentation:
- Endpoint:
https://ollama.com/api
- Authentication: Bearer token in Authorization header
- Environment variable:
OLLAMA_API_KEY
Proposed Solution
Add native support for Ollama Cloud API:
- Support API key authentication in the
ollama provider
- Document configuration for both local and cloud Ollama
- Handle Authorization header properly when
apiKey is provided
Use Case
Users who want to:
- Test out an LLM completely for free through Ollama's limited cloud access before paying for it on something like OpenRouter
- Use Ollama's cloud-hosted models (e.g.,
gpt-oss:120b-cloud) without running local hardware
- Reduce latency by connecting directly to Ollama Cloud instead of routing through a local Ollama instance
Related Issues
Documentation References
Question: Has anyone successfully configured the ollama provider for Ollama Cloud? Would the maintainers prefer enhancing the existing ollama provider or creating a separate ollama-cloud provider?
Problem Description
Currently, Nanobot's
ollamaprovider is designed for local Ollama instances (no auth). Users can already access Ollama Cloud models by routing through a local Ollama instance, but this potentially adds unnecessary latency and requires running local infrastructure. There's no documented way to connect directly to Ollama's cloud API.Ollama Cloud API Details
From Ollama's documentation:
https://ollama.com/apiOLLAMA_API_KEYProposed Solution
Add native support for Ollama Cloud API:
ollamaproviderapiKeyis providedUse Case
Users who want to:
gpt-oss:120b-cloud) without running local hardwareRelated Issues
Documentation References
Question: Has anyone successfully configured the
ollamaprovider for Ollama Cloud? Would the maintainers prefer enhancing the existingollamaprovider or creating a separateollama-cloudprovider?