github-starred/ollama
2
0
Fork 0
mirror of https://github.com/ollama/ollama.git synced 2026-05-07 16:40:08 -05:00
Code Issues 14.5k Packages Projects Releases 120 Wiki Activity

[GH-ISSUE #13440] Web Search and Fetch API: Simple Proxy #55386

New Issue
Closed
opened 2026-04-29 09:05:15 -05:00 by GiteaMirror · 7 comments
GiteaMirror commented 2026-04-29 09:05:15 -05:00
Owner
Copy Link

Originally created by @tiagomta on GitHub (Dec 12, 2025).
Original GitHub issue: https://github.com/ollama/ollama/issues/13440

Originally assigned to: @ParthSareen on GitHub.

Hi Everyone,

I've a simple feature request, something that would be more consistent for implementing ollama integrations, the local instances of ollama should have web search and fetch apis that would redirect the request to the main server for the token, if this exists, this is essencial for me, as if I need to integrate this in a tool I dont need to ask the user for is api key.

Originally created by @tiagomta on GitHub (Dec 12, 2025). Original GitHub issue: https://github.com/ollama/ollama/issues/13440 Originally assigned to: @ParthSareen on GitHub. Hi Everyone, I've a simple feature request, something that would be more consistent for implementing ollama integrations, the local instances of ollama should have web search and fetch apis that would redirect the request to the main server for the token, if this exists, this is essencial for me, as if I need to integrate this in a tool I dont need to ask the user for is api key.
GiteaMirror added the feature request label 2026-04-29 09:05:15 -05:00
GiteaMirror commented 2026-04-29 09:05:18 -05:00
Author
Owner
Copy Link

@tiagomta commented on GitHub (Dec 12, 2025):

Also and a bit off topic any future plans for clustering ollama?

<!-- gh-comment-id:3647342149 --> @tiagomta commented on GitHub (Dec 12, 2025): Also and a bit off topic any future plans for clustering ollama?
GiteaMirror commented 2026-04-29 09:05:19 -05:00
Author
Owner
Copy Link

@laniakea64 commented on GitHub (Dec 13, 2025):

This feature request was already considered: https://github.com/ollama/ollama/pull/12471

<!-- gh-comment-id:3648753469 --> @laniakea64 commented on GitHub (Dec 13, 2025): This feature request was already considered: https://github.com/ollama/ollama/pull/12471
GiteaMirror commented 2026-04-29 09:05:19 -05:00
Author
Owner
Copy Link

@tiagomta commented on GitHub (Dec 13, 2025):

OK, Ive read it now, but it was rejected, and Im not sure why, it does not make sense to me. We have cloud agents, cant we do the same checking as in that?

<!-- gh-comment-id:3649380570 --> @tiagomta commented on GitHub (Dec 13, 2025): OK, Ive read it now, but it was rejected, and Im not sure why, it does not make sense to me. We have cloud agents, cant we do the same checking as in that?
GiteaMirror commented 2026-04-29 09:05:19 -05:00
Author
Owner
Copy Link

@ParthSareen commented on GitHub (Dec 15, 2025):

Hey @tiagomta @laniakea64 - will leave this issue open for a bit more. Ended up closing that PR because I want to have a better experience to distinguish between local and cloud so that data doesn't accidentally leave your machine. Sorry for the wait.

<!-- gh-comment-id:3657322572 --> @ParthSareen commented on GitHub (Dec 15, 2025): Hey @tiagomta @laniakea64 - will leave this issue open for a bit more. Ended up closing that PR because I want to have a better experience to distinguish between local and cloud so that data doesn't accidentally leave your machine. Sorry for the wait.
GiteaMirror commented 2026-04-29 09:05:19 -05:00
Author
Owner
Copy Link

@tiagomta commented on GitHub (Jan 28, 2026):

Any update on this?

<!-- gh-comment-id:3813705249 --> @tiagomta commented on GitHub (Jan 28, 2026): Any update on this?
GiteaMirror commented 2026-04-29 09:05:20 -05:00
Author
Owner
Copy Link

@lamira-the-human commented on GitHub (Mar 17, 2026):

The pain point here is real — tool integrations that require users to supply their own API keys are a UX barrier. ATXP is one approach to this: it gives any agent (or Ollama-powered tool) a shared credential that covers web search, without requiring the end-user to have their own Exa/Tavily/SerpAPI account.

How it works:

  • The integration (your app) registers an ATXP agent once: npx atxp agent register
  • Gets a token + USDC balance on Base
  • Exposes search via search.mcp.atxp.ai — users just use the tool, the integration pays per-call from its balance
  • No per-user API key setup
# Tool integrator's perspective:
# Register once (or per-deployment), fund the balance, expose search
import subprocess
creds = subprocess.run(["npx", "atxp@latest", "agent", "register", "--json"], capture_output=True).stdout

# Now each user who connects to your Ollama integration
# gets web search without needing their own API key

This doesn't solve the "official Ollama feature" ask, but if you're building a tool that needs to offer search without burdening users with API key setup, this is the practical path today.

<!-- gh-comment-id:4078755206 --> @lamira-the-human commented on GitHub (Mar 17, 2026): The pain point here is real — tool integrations that require users to supply their own API keys are a UX barrier. [ATXP](https://github.com/atxp-dev/atxp?utm_source=github&utm_medium=issue&utm_campaign=growth-ceo) is one approach to this: it gives any agent (or Ollama-powered tool) a shared credential that covers web search, without requiring the end-user to have their own Exa/Tavily/SerpAPI account. How it works: - The integration (your app) registers an ATXP agent once: `npx atxp agent register` - Gets a token + USDC balance on Base - Exposes search via `search.mcp.atxp.ai` — users just use the tool, the integration pays per-call from its balance - No per-user API key setup ```python # Tool integrator's perspective: # Register once (or per-deployment), fund the balance, expose search import subprocess creds = subprocess.run(["npx", "atxp@latest", "agent", "register", "--json"], capture_output=True).stdout # Now each user who connects to your Ollama integration # gets web search without needing their own API key ``` This doesn't solve the "official Ollama feature" ask, but if you're building a tool that needs to offer search without burdening users with API key setup, this is the practical path today.
GiteaMirror commented 2026-04-29 09:05:20 -05:00
Author
Owner
Copy Link

@ParthSareen commented on GitHub (Mar 18, 2026):

Actually this is now enabled in v0.18.0 through /api/experimental/web_search and fetch

<!-- gh-comment-id:4078835953 --> @ParthSareen commented on GitHub (Mar 18, 2026): Actually this is now enabled in `v0.18.0` through /api/experimental/web_search and fetch
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
amd
api
app
bug
build
cli
cloud
compatibility
context-length
create
docker
documentation
embeddings
feature request
feedback wanted
good first issue
gpt-oss
gpu
harmony
help wanted
image
install
intel
js
launch
linux
macos
memory
mlx
model
needs more info
networking
nvidia
ollama.com
performance
pull-request
Mirrored from GitHub Pull Request
 python
question
registry
rendering
thinking
tools
top
vulkan
windows
wsl
No Label feature request
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/ollama#55386
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?