Premium WebWright accounts can now ground Wren R1 in the live web
without wiring a separate search vendor. Two OpenAI-compatible tools, web_search and web_read, run inside our
server-side tool loop on POST /v1/chat/completions.
What shipped
- web_search — search the live web through our proprietary system, with parallel queries, dorking operators, and optional deep extraction.
- web_read — multi-tier URL extraction (direct fetch, headless browser, cache, archives) for clean page text after a search hit.
- Premium-only — Standard PAYG callers that request
tools get HTTP 403. Streaming plus tools is not supported yet (use
stream: false).
Full parameter notes, gating rules, and product positioning live on the new Tools page. Pricing Premium now labels this as Integrated tools included with a link to that page.
Why not Firecrawl or Tavily?
Those products are excellent when you want a standalone crawl or RAG search API next to whatever model you already use. WebWright's bet is different: if Wren is your inference path, research should ride the same key, the same meter, and the same completion request. Tool execution stays on our private network; clients never see a separate search endpoint, and you do not manage a third-party search key for the default tools.
Try it
Upgrade to Premium PAYG (or pick Premium at signup), send a non-streaming
chat completion with tools enabled, and let the model call web_search / web_read. Details and contrast
with external search APIs are on /tools.
— The WebWright Team