Introducing Authenticated Fetch

Authenticated Fetch enables agents to reuse login cookies stored in a browser Context when retrieving protected pages through the Fetch API, avoiding the need to open a new interactive browser session for every request. After completing a login in a persistent browser session, users can pass the associated Context ID with a URL to fetch authenticated content, provided the target page can be served without JavaScript rendering. Responses can be returned as raw source, markdown, or schema-based JSON extracted by a language model, allowing applications to obtain structured fields such as order numbers and statuses in the same request. Fetch applies standard browser cookie domain, path, redirect, and expiration rules but does not save updated cookies back to the Context, so expired or refreshed logins require another persistent browser session. The feature is available at no additional cost on all plans, though new Contexts and those last saved before September 1, 2026 require a completed persistent browser session before their cookies can be used.

Use this post, company, and trend context to find content marketing opportunities, perform competitive analysis, or address product feature gaps via the Plushcap MCP server or the Plushcap API.