Loading video...

Video Failed to Load

Go Home

pi-web-access update: the agent can now search, then pull specific values off a page instead of reading the whole thing. Clairic returns just what you asked for, with the line it came from, and flags anything it isn't sure of. When in codemode the values come back as typed...

18,145 views • 6 days ago •via X (Twitter)

14 Comments

Kipoo's profile picture
Kipoo6 days ago

nice job, 我觉得pi-web-access可以成为pi的内置插件

.'s profile picture
.6 days ago

web access and generally speaking, file/computer access, should be a default functionality in Pi agent

Ruben's profile picture
Ruben6 days ago

Thank you @nicopreme. What resources would you reccomend for understanding how agents use web search and its different variations? I could not find any comprehensive review.

Diego Cerdan's profile picture
Diego Cerdan6 days ago

Thank you for the Pi extension. Looking good! I will try it out and maybe replace my current custom SearXNG skill.

HM's profile picture
HM6 days ago

Keeping the source line is the good part. For prices, I'd want the billing period and 'starting at' qualifier attached too. A clean number can be misleading on its own.

Sandip Bhattacharya 🌏✌️'s profile picture
Sandip Bhattacharya 🌏✌️6 days ago

Is this an exact string/regex match on the content? or a subagent based semantic extraction?

kayce's profile picture
kayce6 days ago

有点像codemode了

Veyro's profile picture
Veyro6 days ago

The uncertainty flag is the part I'd want to keep in the typed result too. A script needs to distinguish “not found” from a confidently extracted zero.

Niko Petrov's profile picture
Niko Petrov6 days ago

Cutting tool tokens by 60% is huge, context window was killing us.

Jonathan Vital's profile picture
Jonathan Vital6 days ago

What a gain!!

Ravi's profile picture
Ravi6 days ago

an agent that grabs the one value it needs and shows the line it came from already reads docs better than most of us

Web制作出身のAI・Webアプリ開発者's profile picture
Web制作出身のAI・Webアプリ開発者5 days ago

全文を渡さず、必要な値と根拠の行だけを返し、不確かな箇所も示す設計は、調査の速さと検証しやすさを両立できますね。エージェントに任せる範囲を広げても出典を追えるのは、実務で大事だと思います。

Peter Dove's profile picture
Peter Dove6 days ago

Nice. Targeted extraction should cut token waste and simplify price scripts

BreezeOg's profile picture
BreezeOg6 days ago

does it ever pull the wrong value and still show a source

Related Videos

🚨 THIS IS ACTUALLY INSANE Your AI agent can have access to the web. But if it can't reliably read what’s actually on the page, that access is almost useless. We looked at Firecrawl as the web layer for AI agents and the numbers are hard to ignore. The setup is simple: Give it a URL, search query, or website. Firecrawl handles the ugly part — crawling, scraping, rendering, extracting, and turning web content into something an AI model can actually use. The headline numbers: → 173,000+ GitHub stars → Search, scrape and interact with the web at scale → Supports web pages, PDFs, DOCX and other content → Structured data extraction for AI workflows → MCP support for connecting it directly to AI agents The workflow looks like this: Search → Scrape → Crawl → Extract → Feed the agent Three things stand out: 1. Scraping becomes an infrastructure layer Instead of maintaining your own pile of HTTP clients, parsers, browser automation and retry logic, you can treat web access as an API. 2. Agents get more than raw HTML The goal isn't just downloading a webpage. It's turning messy web content into clean context that an LLM can reason over. 3. The same layer works across different agent workflows Research agents. RAG pipelines. AI search. Competitive intelligence. Web-data extraction. The interesting shift: AI agents don't just need better models. They need better access to the information those models are supposed to reason about. Firecrawl is building that layer. Save this repo.

Vikas gupta

20,121 views • 1 month ago

Stop paying $20–50/month for your AI agent to browse the web. i built the free version no API keys, no config, no rate limits😳 it's called Hound. An MCP server that does fetch, search, crawl, and screenshot — all keyless and now it ships a native Pi extension, so you get all 6 tools as first-class Pi tools, not through a generic MCP adapter what you get: → web_fetch — anti-bot fetch → clean markdown. PDFs get section maps + auto-OCR. Dead pages auto-recover from the Internet archive (honestly marked, never pretending it's live) → web_search — 10 keyless backends in parallel (DuckDuckGo, Brave, Mojeek, Yandex, Google…) + a local neural reranker → web_crawl — best-first same-domain walk. sitemap mode maps a whole site in one fetch → web_screenshot — anti-bot shots for multimodal models → cache_clear + hound_version what it replaces: -tavily — free tier -firecrawl — $16–50/mo -searXNG + browser + extractor glue — fragile -hound — $0, keyless, forever why it matters: >agent research needs web access, but everyone gates it behind a key or a limit >hound is honest about errors — a 404 says "Page doesn't exist" instead of dumping an error page as if it were content >archive recovery tags source= so the agent knows the content is historical, not live 2-minute setup: -pip install hound-mcp[all] -pi install npm: @houndmcp/hound-mcp-pi -/reload → tools are live. That's it Caveats (read): dataDome, Akamai, Cloudflare Turnstile — no free tool bypasses these hound tries the stealthy browser, then tells you to switch sources the [all] extra is ~100MB (onnxruntime + OCR). Works without it, but full install is recommended not a scraping-at-scale tool. Crawl caps at 100 pages by default — built for agent research Give your agent the web for free

Nahid

45,466 views • 3 months ago