Last updated September 23, 2026.
Evercraft Web Fetch processes the public URL a user or agent explicitly asks it to retrieve and the public response content needed to return that result. The fetch primitive does not send user cookies, passwords, API keys, authorization headers, or browser-session credentials to the requested site.
The service may process basic request, DNS, network, error, timing, and response metadata needed for security, reliability, abuse prevention, and evidence. The tool response includes the final URL, redirect hops, content type, status, byte count, truncation state, retrieval time, and a SHA-256 hash of the retrieved bytes.
Credential-bearing URLs, IP-literal targets, local/private hostnames, and DNS answers in blocked private or local network ranges are rejected. Redirect targets are revalidated before retrieval.
Search, browser automation, and authenticated-browser features are not represented as live in this version. Any future authenticated browsing must use explicit user authorization and credential isolation.