This public beta exposes the same validated operations through its human interface, REST API, Remote MCP and WebMCP. Connectivity is not invocation certification.
REST + OpenAPI
Open the OpenAPI 3.1 document →POST JSON to /api/v1/[operation]. Read operations use POST so private access tokens stay out of URLs.
Remote MCP
/api/mcpStateless JSON-RPC over HTTP. Supports discovery, initialize, tools/list and tools/call. Public endpoint; saved records require their private access token.
WebMCP
Registers the same four tools with document.modelContext, or navigator.modelContext when available. Unsupported browsers retain the ordinary interface.
create_funnel_game
Analyze public page HTML for potential funnel friction, or create three proposed funnel concepts. Use for a business the user owns or manages. Not a full visual audit, market research, diagnosis, or conversion prediction. demo=true uses a fictional electrical business. Missing facts stay unknown.
get_funnel_game
Read a previously created game with its returned id and private access token. Do not invent either value.
save_funnel_plan
Save a user-requested result to their explicitly supplied email. Requires consent=true. Does not subscribe to marketing or book a session. Email delivery may be unconfigured; report returned delivery status accurately.
request_funnel_strategy
Record an explicitly requested strategy-session follow-up. Requires supplied email and consent. This is a request, not a confirmed booking.
Boundaries and launch connections
The scan reads public HTML. It does not take screenshots, submit forms, log in, or observe real conversions. Low-confidence findings require human review. Website-derived dialogs are proposals, not completed deep research.
DSN anonymous telemetry is enabled. Email sender, booking calendar and visual-browser audit service are not connected. Sample monitoring is illustrative. The demonstration does not run ads or send follow-up campaigns.