Agent Connect · Live

Agents visit your website.
Give them approved answers.

Agent Connect connects visiting, communicating browser agents with business facts you approve. Add it alongside AI Lead Agent, or install it on its own without a chat interface.

Agent Connect is live. Approve your business facts, connect your website and manage access from your account.

Two website installation pathsRead-only browser answersOptional native discovery & distribution

Your website is the starting point

One business.
Two ways to connect.

Keep the facts under your control. Choose the website experience that fits your business, then test what really communicates.

Share what you approve

Review business facts and their supporting evidence before making them available. The connection is for approved information, not unrestricted access to your account.

AI Lead Agent + Agent Connect

Chat for people and approved answers for supported agents. Reuse the existing widget for your mapped business location—no second Agent Connect snippet.

Agent Connect only

Install the supplied ownership meta tag and lightweight page script. No customer chat interface is added; only the explicit owner test panel displays a testing UI.

Discovery, not directory enrollment

Host your native agent card on your own domain. Optional native client setup and distribution stay separate; neither is required to begin your website setup.

Setup, in plain English

Prepare the facts.
Connect the page.
Test the exchange.

For owners and agencies who want to distinguish an installed script from a real, supported exchange. No website changes are made automatically.

Sign in to manage Agent Connect
  1. Reuse your business information

    Start with existing details or add them directly. Optionally scan your website to help gather candidate facts.

  2. Approve facts and connection capabilities

    Check your sources, approve the business facts you want to share and enable the connection for your business.

  3. Choose and manually install your connection

    Start with the website saved for your business. Reuse a mapped, enabled AI Lead Agent widget, or install the standalone ownership tag and snippet. No authorized website integration is connected; you or your administrator makes the change.

  4. Check HTML, then test your actual page

    Verify the public embed and native discovery card separately. Open your page’s owner test panel to run a real network request and test native WebMCP where supported. Review observed communication without treating it as vendor certification.

Capabilities & boundaries

An installed page.
An observed exchange.
Different evidence.

Agent Connect is a controlled connection, not a claim that every assistant can use your website.

Browser page tool · Public, read-only evidence
Supported visiting agents can ask for approved facts. Browser registration is self-reported; an endpoint exchange is an observed request. Neither independently validates browser vendor support. No browser inquiry submissions.
WebMCP & explicit page API · Support-dependent
Experimental document.modelContext, with navigator.modelContext as a legacy fallback, depends on secure context, tools policy, browser support, and an origin trial or Chrome flag. Clients must explicitly support window.AdGizmoAgentConnect.ask to use the fallback page API.
Native discovery & authenticated connections · Separate
Manually host /.well-known/agent-card.json for native domain discovery. Keep business-scoped credentials private. Native MCP remains read-only; authenticated A2A inquiries require customer consent and owner approval before becoming CRM leads.
Not a listing service. Not autonomous booking.

No enrollment in ChatGPT, Claude, or a Registry. Gemini is unsupported. No automatic bookings, outbound messages or guaranteed recommendations.

A file on your domain

Native discovery starts with your host.

Download the secret-free agent-card.json. Publishing that file is a manual website task, not an assistant listing.

Static hosting
Upload the supplied JSON at /.well-known/agent-card.json. Return status 200 and application/json MIME type, without redirects.
nginx or Next.js
Use an exact nginx location for the file, or a Next app route returning the supplied JSON at that exact path. Both need the same 200 status and JSON content type.
WordPress or a custom-code builder
Use your WordPress host’s file tools, not the page editor. A custom-code-only builder needs a host route integration; an embedded script cannot publish the well-known JSON route.
Distribution is optional. Secrets stay private.

Native client setup and distribution are advanced, separate steps. Never add a private credential to your public card or page. Native connections require owner approval and business-scoped authentication. Directory enrollment and publishing files on your website remain separate steps.

Good questions, straight answers

Before you connect

Do I need AI Lead Agent or a chat widget?

No. Choose AI Lead Agent plus Agent Connect to reuse an existing mapped widget, or Agent Connect only for a page connection without chat. The standalone path requires the supplied ownership meta tag and script on your page. You can still prepare approved facts and optional native client setup without a website.

Does this list my business in ChatGPT or Claude?

No. Agent Connect does not enroll your business in ChatGPT, Claude, or an agent registry. A compatible external client must be configured and connected. There is no promise that an assistant will discover, recommend, or send traffic to your business. Gemini is unsupported.

What can a connected agent do?

The public browser page tool reads approved business evidence; it cannot submit inquiries. Separately, compatible authenticated native clients can use MCP for read-only facts and A2A for text follow-ups and consent-based inquiries, subject to existing owner approval. No channel has general access to your CRM.

Does a verified installation prove browser support?

No. We check the actual public page HTML without running JavaScript or following redirects. Browser channel registration is self-reported, and a recorded endpoint exchange only shows that a request occurred. Neither independently validates browser vendor support. Open the owner test panel on your page to run an actual page request and test native WebMCP where supported.

Which browser agents can use it?

WebMCP is experimental: document.modelContext is the latest API, with navigator.modelContext as a legacy fallback. Availability depends on a secure context, tools policy, browser support, and an origin trial or Chrome flag. The window.AdGizmoAgentConnect.ask fallback is only for clients explicitly supporting our page API. This is not universal browser support or universal A2A.

How do native agents discover my website?

Manually host the supplied agent-card.json at /.well-known/agent-card.json on your domain, with status 200 and application/json MIME type, without redirects. A script alone cannot create that route. The native card retains private scoped authentication for native A2A; never put secrets in the public file. Discovery is separate from optional distribution and does not guarantee an agent will visit.

Does an inquiry automatically become a lead?

No. The customer must consent to sharing an inquiry. You review it and approve it before it becomes a CRM lead. An inquiry is not a confirmed booking.

Can it book appointments or send messages for me?

No automatic bookings or outbound messages are included in this connection. Agent Connect shares approved information and supports controlled inbound inquiries.

Is Agent Connect live, and how do I get started?

Yes. Sign in to AdGizmo, review and approve your business facts, then set up your website connection. Check pricing or contact AdGizmo for the features and access included in your account.

Your next step

Explore a connection that stays in your control.

Set up Agent Connect for your business, or talk through the website connection and compatible client options with us.