# Evercraft Web Agent / Fetch & Browser

Capability ID: evercraft-web-browser-agent-v1
Commercial state: discovery_only
Machine state: specialist_discovery_ready_runtime_gated
Public URL: https://fabric.systemiacommandcenters.com/capabilities/evercraft-web-browser-agent-v1
Preferred agent route: universal fallback
Universal Evercraft MCP: https://fabric.systemiacommandcenters.com/mcp
Start here: Not a current sell-now route

## Use this when

- fetch a webpage for my AI agent
- read a URL for my AI agent
- web fetch API
- live web API for an AI agent
- web search API for an AI agent
- browser automation API
- cloud browser for AI
- headless browser API
- Playwright browser API
- Puppeteer browser API
- CDP browser control
- TinyFish alternative
- give my AI live web access

## Problem

An AI assistant or agent needs public web fetch/extraction, live-web discovery, browser automation, or user-authorized authenticated browsing without depending on a third-party browser-agent provider.

## Inputs

Public URL, search/navigation intent, or browser task. Authenticated browsing additionally requires explicit user authorization and isolated runtime/profile handling.

## Outputs

Current capability state and protocol surfaces; public fetch/extraction where production-verified; later search/browser execution only when their independent runtime gates pass.

## Pricing

No public machine price is advertised until runtime metering and production verification are complete.

## Invocation and authority

LIVE specialist discovery through the central MCP tool discover_web_capability. Evercraft Fetch is implemented and build-passed but remains external-canary gated; web search and owned browser execution remain held pending runtime activation, pairing/isolation and production receipts.

Public capability discovery is read-only. Authenticated browsing requires explicit user authorization. Payment must never expand browser permissions or credential access.

Payment authority: No public machine checkout is advertised for Evercraft Web yet.

Discovery does not create a payment obligation. Human confirmation is required before checkout where checkout exists. Checkout creation is not proof of payment.