InfiniteWatchAgent Ready Web
IW AGENT READY WEB

www.wefox.com
MCP & WebMCP readiness.

Discover how easily AI assistants can find your business and help customers take action.

Run a fresh check. Updates are limited to once every 15 minutes.
www.wefox.com19 documents checked16:06 UTC

Your website’s AI readiness

23 checks · 6 categories

We check public information without submitting forms or taking actions on your website.

Start the conversation with your team.

www.wefox.com · 81/100 · 2026-09-24

LESS FRICTION. MORE MOMENTUM.

From browsing pages to getting an answer.

Illustrative scenario
4 steps1 guided action

Connect your useful information to a guided enquiry, product choice or service request.

See the journey assumptions
  1. Explore the website
  2. Find information
  3. Compare options
  4. Take the next step

The proposed action brings these steps into one guided interaction. This is an example, not measured performance of this website.

Explore time savings and calculation assumptions
CUSTOMER TIME

How much time could your customers save?

www.wefox.com · Finding information

Based on this website
Estimated time saved
4.1seconds saved

per customer task

72.3% less estimated waiting
Estimated task duration

Page-by-page journey

5.6s

4 estimated steps × 1.4s per step

With a proposed AI shortcut

1.6s

1 estimated step × 1.6s per step

Compares an AI assistant navigating pages with a proposed direct action. These are projections; we haven’t timed the task or confirmed that a discovered tool can complete it.

Adjust task steps and timing

Match these assumptions to the same completed customer task in both journeys.

Page-by-page journey
With a proposed AI shortcut

Task duration = steps × seconds per step. Each step includes assumed processing and request time.

Technical detail: token use

Tokens estimate the amount of content the AI processes.

Estimated token difference per task5,783 more tokens

397.2% more token use.

Page-by-page journey 1,456 tokens

With a proposed AI shortcut 7,239 tokens

Page-by-page journey
With a proposed AI shortcut

Tokens per task = steps × tokens per step + one-time context setup. Token changes do not change the timing assumptions.

Scan evidence: about 364 readable context tokens and 6,779 tool schema tokens.

How this website’s estimate was built
Observed page request
0.21s
Controls found
5
Forms found
0
Tool definitions found
9
  • The browser model assumes readable text plus 24 tokens per control is sent on every step without caching. Raw HTML size is not used as the default context; agents may send smaller snapshots or diffs.
  • Token sizes are approximated from retrieved characters ÷ 4; no model tokenizer was run.
  • Browser steps assume navigation, 1 input decision, submission and reading. These steps were inferred, not executed.
  • Setup overhead uses all discovered tool schemas. The comparison models a proposed one-call page interaction; discovered tools have not been verified to support this same task.
  • Each step assumes 1.2 seconds of model processing. Browser network time uses this page’s HTTP request; tool time uses the metadata-listing request. Neither is a measured customer workflow.
  • Tool argument/result tokens use an editable 400-token allowance plus 60 tokens per modeled input. Cached context, retries and real output sizes can change savings.
EXPLORE MORE COMPANIES

See how other websites compare.

Explore other companies’ AI readiness reports. Search for a website or browse by industry to find ideas for your next customer journey.

Explore the directory ↗
YOUR BUSINESS OPPORTUNITY

Turn customer intent into action.

Customer journeys

Make my website agent-ready ↗
01

Help customers find answers and take the next step

Connect your useful information to a guided enquiry, product choice or service request.

What supports this opportunity

Proposed customer journey. Public signals guide the implementation.

Customer actions listed for AI · Detected

9 tool entries were listed by 1 public MCP endpoint(s). No tools were executed.

Clearly explained actions · Detected

Tool names and description signals found. Source checks do not prove runtime completeness.

Required information for each action · Detected

Structured tool input declarations detected. Schema correctness needs runtime review.

Action safety information · Detected

Tool behavior annotations detected. Hints are not a security boundary.

02

Get discovered with the right answer

Help assistants understand your offer and point customers towards the next useful action.

What supports this opportunity

Proposed customer journey. Public signals guide the implementation.

Clear page title · Detected

Title: Home | wefox

Search description · Detected

A descriptive meta description is present.

AI content guide (llms.txt) · Detected

A public llms.txt document was found.

Instructions for connecting AI assistants · Detected

MCP documentation links or endpoint configuration are publicly discoverable.

Content labels AI can understand · Detected

Parseable schema.org JSON-LD found. Content accuracy requires editorial review.

03

Make the next step easier

Give customers and assistants a clear route from interest to an enquiry or purchase.

What supports this opportunity

Proposed customer journey. Public signals guide the implementation.

Clear page structure · Not detected

Organize the page around a clear main heading and identifiable content sections.

Easy-to-follow navigation · Detected

17 labelled, crawlable link(s) found.

Clear button and form labels · Not detected

Give each form field and button a clear label so its purpose is easy to understand.

WHAT AI ASSISTANTS CAN USE

Actions AI assistants can find

Tools let AI assistants help with tasks such as finding a product or checking an order. These are the public integration signals we found; task completion still needs testing.

0Browser integration sources
9Publicly listed AI tools
UnverifiedBrowser integration signals
Explore the tools and technical evidence

WebMCP connects AI assistants to actions in a browser. MCP lets compatible assistants connect directly to a service. The details below help your technical team evaluate both.

Tool list retrieved from the public MCP server. No tools were executed. View endpoint ↗

ReadFullDocsArticle

Fetches the full Wix docs article or method article with code examples for using the method. Docs articles looks like this: https://dev.wix.com/docs/... and they can either be general docs articles or method articles. For REST docs, use the URL as-is. For SDK docs, the URL SHOULD include ?apiView=SDK. <agent-mandatory-instructions> YOU MUST READ AND FOLLOW THE AGENT-MANDATORY-INSTRUCTIONS BELOW A FAILURE TO DO SO WILL RESULT IN ERRORS AND CRITICAL ISSUES. <goal> You are an agent that helps the u

Inputs: articleUrl
Remote MCP

ReadFullDocsMethodSchema

Fetches the full method schema for a given method. This will give you the entire request/response schema with all the fields and their descriptions. For REST API methods, prefer SearchWixAPISpec when it is available: it can fetch and inspect the exact method schema by docs URL, return the request/response shape, and inspect selected nested component schemas without dumping unrelated fields. Use ReadFullDocsMethodSchema for REST only when SearchWixAPISpec is unavailable or did not provide the nee

Inputs: articleUrl, reason
Remote MCP

BrowseWixRESTDocsMenu

Browse the Wix REST API documentation menu hierarchy. Alternative to SearchWixRESTDocumentation - use this to explore and discover APIs by navigating the menu structure instead of searching by keywords. - Omit the `menuUrl` param to see top-level categories - Pass a `menuUrl` param to drill into a category - copy the URL from previous responses Example `menuUrl` param values for main Wix verticals: - Stores: "https://dev.wix.com/docs/api-reference/business-solutions/stores" - Bookings: "https://

Inputs: menuUrl, reason
Remote MCP

CallWixSiteAPI

Call apis on site "wefox" (https://www.wefox.com/_api/mcp). Use this to perform an action on visitor's behalf, for example, query the site's data or book an appointment. Before calling this tool, you should ALWAYS check the rest docs (use "SearchSiteApiDocs" tool) for the specific API you want to call. The mentioned tool will give you instructions how to use the API.', 'NEVER try to guess the API or endpoint, ALWAYS check the docs using "SearchSiteApiDocs" tool. The url param should be tak

Inputs: visitorToken, url, method, body
Remote MCP

GenerateVisitorToken

Create a new visitor session and obtain a visitor access token for site "wefox" (https://www.wefox.com/_api/mcp). You must use this tool before calling CallWixSiteAPI for this first time. If you already have a visitor token in your context, DO NOT USE THIS TOOL AGAIN.

Remote MCP

SearchSiteApiDocs

Searches for site "wefox" (https://www.wefox.com/_api/mcp) API documentation and returns how to use the site using the API. You are a helpful "wefox" site assistant chatbot and you are helping the user perform actions on the site - to query the site's data or to perform an action on the site. Specify the API endpoint, resource, or action you need information about (e.g., 'get site details endpoint', 'create data collection', 'update product API', 'REST authentication'). If you can't find what yo

Inputs: searchTerm
Remote MCP

GetBusinessDetails

Get business and site details for "wefox" (https://www.wefox.com/_api/mcp). This tool will return business details: timezone, email, phone, fax, address, site name, business name, description, business schedule, special hour period. It will also return site features that you can use via other tools (bookings, store, etc.). Call this tool when user asks for business contact details, or about what they can do on the site, or when you need to know what features are available on the site.

Remote MCP

SearchInSite

Searches the site "wefox" (https://www.wefox.com/_api/mcp) for information. Use this tool ONLY in the following cases: 1. You just used "GetBusinessDetails" tool and you did not find the information you need. 2. User asked a generic business question about their business (e.g., business address, business hours, contact information, return policy, etc.) 3. You already tried to find an entity (e.g., product, service, etc.) using an API tool and you did not find the information you need. 4. The req

Inputs: searchTerm
Remote MCP

ExecuteWixAPI

Run JavaScript against the Wix REST API on site "wefox" (https://www.wefox.com/_api/mcp), on the visitor's behalf. The code runs in a sandbox and you get back whatever it returns. PREFER THIS TOOL OVER CallWixSiteAPI. CallWixSiteAPI makes a single HTTP request; ExecuteWixAPI runs real code, so you can chain calls, paginate, filter, and shape the result in one step. Use ExecuteWixAPI for any Wix API work on this site, and fall back to CallWixSiteAPI only for a trivial one-shot read where code ad

Inputs: code, reason, hasMutations, sourceDocUrls, visitorToken
Remote MCP

0 named source declarations found. Counts cover the sampled page and advertised endpoints. Source declarations are not runtime-tested tools; entries listed through more than one route may overlap.

WebMCP directory · webmcp.com

No matching listing was found on webmcp.com. This does not establish that the website lacks WebMCP.

Open webmcp.com ↗

This is a stored directory snapshot, not a live tool test. Its count may include browser-only tools and may differ from the public MCP server count. Directory listings do not change your score.

MCP Registry

Registry lookup could not be verified.

MEET AGENTS WHERE THEY ARE

Where can customers use AI assistants?

Support varies by browser and assistant. Some connections are still experimental; this is a platform guide, not a test of your website.

Reviewed Sep 2026
See browser support and connection options

Google Chrome

149+ · origin trial

WebMCP requires an eligible origin trial or the experimental testing flag. A compatible agent is also required.

Support details

Microsoft Edge

150+ · origin trial

Available for experimentation through the Edge origin trial. Check trial eligibility and current expiry dates.

Support details

Brave / Leo

Experimental integration

Experimental Leo integration is reported by the specification project. Availability is not guaranteed for all users.

Support details

Mozilla Firefox

No confirmed release

Prototype work is tracked, but no native release is confirmed. Use standard browser automation or a remote MCP client.

Support details

Apple Safari

No confirmed native support

Native WebMCP cannot be assumed. Regular browser automation and separate remote MCP clients remain alternatives.

Support details

Remote MCP clients

Browser-independent

Compatible agents can connect directly using a supported transport. Authentication and permissions still apply.

Support details

Remote MCP is a separate route. A compatible agent can use a remote MCP server independently of the visitor’s browser. Browser automation can still use regular pages. This matrix describes platform support, not a cross-browser test of your website.

UNDERSTAND YOUR SCORE

A clear starting point for your team.

Can AI assistants find your website, understand what you offer and help customers act? Your score brings these signals together and shows where a closer look is needed.

LESS WAITING. FEWER STEPS.

Let customers get things done through AI.

Bring quoting, booking and product discovery into AI-assisted customer journeys.

A walkthrough of your website Opportunities to reduce customer effort A practical plan for your team

Make my website agent-ready

See how InfiniteWatch can help your customers do more in less time.

A conversation about your use case. No obligation.