Devil Club: the first site where an AI agent can hire you an LLC

Chatbots read your website. Agents use it. That single difference defines the next generation of the internet — and devil.club just shipped the standard that makes it possible. We're one of the first websites in the world exposing native WebMCP tools directly to the browser.

If you've never heard of WebMCP, don't worry: it has existed in Chrome stable for literally weeks. But understanding what it is will save you time when, in a few months, your favorite AI agent can hire you a US LLC without you navigating to anything.

The problem: blind scrapers vs. blind agents

When you ask Claude, ChatGPT or Gemini to "compare LLC providers for non-residents", today they do one of two things:

1. Search Google and read the top 5 results with a crawler. They load HTML, try to extract prices and features, and make up what they can't find.
2. Use stale training data. Possibly 6, 12, or 24 months old. Outdated prices, services that no longer exist, terms that changed.

Both paths produce plausible but incorrect answers. The user ends up navigating manually to verify — exactly what the agent was supposed to save them from.

The root problem: the web was designed for humans who read, not for machines that act. When an agent needs "the current price of LLC formation with Manager included", it has to guess from HTML. When it needs "to initiate the order flow", it can't — it can only show you a link.

The solution: WebMCP

WebMCP (Web Model Context Protocol) is a standard Chrome introduced in version 146 (February 2026) so websites can expose structured tools directly to the agent. It's not a crawler, it's not scraping, it's not a REST API hidden behind authentication.

It's this: any web page can declare a set of tools with name, description and input/output schema. The browser (Chrome) exposes them to the user's AI agent via document.modelContext. The agent invokes them, receives typed responses, and acts.

WebMCP turns every website into an agent-readable endpoint, with no API key, no fragile scraping, no bilateral negotiation between company and model. The protocol is public, open, and stewarded by the W3C Web Machine Learning Community Group.

For a services website like Devil Club, this changes the game. An agent landing on devil.club no longer has to guess anything: the website itself hands it the catalog, up-to-date prices, and order flows in consumable format.

The 9 tools Devil Club exposes

We've implemented 9 dc_* tools spread across three layers, all live after the May 25 deploy:

Public (no login, discoverable from any page)

• dc_list_services — returns the 15 catalog services with name, tagline, current price and currency. Anti-scraping, anti-stale-price.
• dc_get_service_details — full detail (long description, features, period) for a specific service.
• dc_quote_llc — structured quote for a New Mexico LLC, with or without the Manager plan. No tax surprises, no small print.
• dc_booking_availability — actual open slots in the booking calendar (free Strategic Diagnostic, Advanced Support, Priority Support for members).

Member (require authenticated session)

• dc_my_account — the agent can check your tier, membership status, signup date. Without you opening /miembros.
• dc_my_entities — list of your LLCs with status, plan, formation date. Legacy bridging included.
• dc_my_renewals — what renewals you have coming up and what they cost.

Mutation (only with explicit human confirmation)

• dc_start_llc_order — initiates the LLC order flow. NEVER executes the payment automatically: it opens a native confirmation modal where the user has to click "Continue to wizard", then redirects to /contratar/ with all fields pre-filled. No automatic payment, no order created in DB, no touching Mercury / Wise / Stripe.

The 4 public ones are announced on any page of the site. Member tools require an authenticated session cookie (requireAuth server-side, can't be bypassed). The mutation tool has three layers of protection: per-user rate-limit of 5/hour, durable audit log, and a confirmation modal with explicit text.

Why this matters for a US LLC

Imagine this flow, possible today in Chrome 146+ with the chrome://flags/#enable-webmcp-testing flag enabled:

User: "I'm thinking of opening an LLC for my digital business, I don't want to pay 22% in my country. What do you recommend?"

AI agent: [silently navigates to devil.club, calls dc_list_services and dc_quote_llc({state: 'NM', with_manager: true})] "Devil Club has two main packages in New Mexico: LLC Without Manager at $1,800/year (formation + EIN + RA first year) and LLC With Manager at $3,600/year (includes hardened Operating Agreement, Governance Ledger, annual Tax Filing). Want me to show you slots for a free diagnostic this week?"

User: "Yes, diagnostic."

AI agent: [calls dc_booking_availability({service: 'strategic_diagnostic'})] "There are 8 slots this week. The closest is tomorrow Tuesday at 4:00 PM Asunción time (10:00 AM EST). Does that work for you?"

Zero scraping. Zero guessing. Zero stale prices. All information comes straight from Devil Club's server, with the same freshness a human browsing the site would see.

Demo: how to see it yourself today

If you have Chrome 146 or newer (almost any Chrome stable by now), you can see the registered tools in real time:

1. Open Chrome and go to chrome://flags/#enable-webmcp-testing
2. Set the flag to Enabled and restart the browser
3. Navigate to devil.club
4. Open DevTools (F12) → Console
5. Type: document.modelContext (or navigator.modelContext in Chrome 149 and earlier)
6. You'll see the object with the registerTool API. To see registered tools, check document.modelContext.tools or the equivalent API your Chrome version exposes.

When Chrome ships WebMCP by default (estimated mid-2026 with version 149 stable or the next cycle), any user with Chrome will see this automatically — no flags, no extensions. And AI agents integrated into the browser (Gemini, OpenAI's future Operator, local assistants) will be able to consume them.

Privacy and security: what WebMCP does NOT do at Devil Club

Implementing AI-agent tools has obvious risks. We've designed the system around three principles:

1. Mutations are never automatic

dc_start_llc_order is the only tool that mutates anything. Its technical contract is strict:

• Mandatory confirmation modal — the browser pauses agent execution and shows the user a native <dialog> summarizing the operation. Without a human click, nothing advances.
• Rate limit 5 starts/hour per user — an agent in a loop can't create 1,000 orders.
• Zero automatic payment — the tool only generates a pre-filled URL to the /contratar wizard. The user completes the wizard, the wizard charges. Same as always.
• Durable audit log — every attempt lands in dc.audit_log with actor, timestamp, IP and sanitized metadata (no user email, no PII).

2. No cross-tenant leaks

Member tools (dc_my_*) ALWAYS filter by the session JWT. The agent cannot pass someone else's client_id because the endpoints don't accept that parameter. The only valid identity is the cookie of the logged-in user themselves.

3. No telemetry with PII

Every tool invocation drops a row into dc.metrics_webmcp_calls with 4 fields: tool name, success boolean, latency in ms, and a coarse user-agent bucket (desktop / mobile / tablet / bot / unknown). NEVER the full User-Agent, never emails, never argument contents. The session_id is an ephemeral UUIDv4 generated browser-side (sessionStorage) that dies when the tab closes.

Additionally, the /admin/* zone emits Permissions-Policy: tools=() at the browser level — even if we mistakenly mounted a tool there, Chrome would block its registration. Defense-in-depth.

Ecosystem status: who consumes this today?

Full honesty: almost no one yet. WebMCP is emerging spec. Who supports it as of May 2026:

• Chrome 146+ with manual flag — working today, requires enabling enable-webmcp-testing
• Chrome 149 stable — estimated mid-2026, default activation without flag
• Google's Inspector extension — for QA: webmcp-tools

Commercial agents (Claude.ai web, ChatGPT operator, Gemini integrated in Chrome) don't natively consume WebMCP yet. But the trend is clear: Google moved the API from navigator.modelContext to document.modelContext in Chrome 150 (deprecation announced on May 25, 2026), a signal the W3C considers it stable enough to refine. Agent integration will come in the next 6-12 months.

Implementing it today is betting on the next generation of the internet. When agents arrive, websites that only serve HTML for humans will fall behind. The ones exposing tools will compete for invocations — exactly the way websites today compete for Google clicks.

Why we're one of the first

WebMCP reached Chrome stable in February. The spec is open and published at webmachinelearning.github.io/webmcp. Any website in the world can implement it. The reality is almost no one has done it yet because it requires:

• Having stable REST endpoints already built (not internal scrapers)
• Knowing which tools make sense for your business (it's not a technical decision, it's a product one)
• Designing the confirm-modal flow for mutations (new UX)
• Privacy-correct telemetry from day 1 (can't be added later)

At Devil Club we pulled it off in a week because the rest of the stack was already there: API endpoints existed, the catalog was code (not legacy DB), and the team understood why it matters. The timing was right.

We're writing this blog post now because we want people to know that when agents arrive, Devil Club is already ready. And because, frankly, being the first or second website in the world to do something doesn't happen every day.

Executive summary

If you skipped everything else and just want the key points:

• Devil Club implements WebMCP, the Chrome 146+ standard for AI agents to use your website instead of scraping it.
• 9 live dc_* tools: 4 public (catalog, details, quote, booking), 3 member (account, entities, renewals), 1 mutation (start LLC order with mandatory confirmation).
• No automatic payments, no PII in telemetry, durable audit log, defense-in-depth with browser-level Permissions-Policy.
• Today only testers with the manual flag see it. When Chrome ships by default (~2026 Q3/Q4), any Chrome user.
• We're one of the first websites in the world to do this — bet on the future, not immediate monetization.

If you're interested in the full technical implementation, all PRs are open at github.com/DevilClubES/devil-club under the webmcp label. And if you're interested in the other thing — opening a US LLC with all of this included — keep reading below.