AgenticCart
Docs Setup Domain verification

Domain verification

AI agent domain verification proves you control the storefront. Use WooCommerce pairing or add a DNS TXT record before your agent goes live on a domain.

AI agent domain verification is how AgenticCart confirms you control the domain where the shopping assistant will appear. It keeps your AI sales agent tied to your brand and unlocks the hosted chat domain flow on your own URL.

INFO

Domain verification proves ownership of the domain where the hosted chat page will run. It is the prerequisite for AgenticCart to issue managed SSL for your custom subdomain.

Why AgenticCart verifies domains

Verification protects your brand and your shoppers. Once a domain is verified, only your account can run an AI sales agent there, which means:

  • Nobody else can point the AgenticCart hosted chat at a lookalike subdomain of your brand.
  • The hosted chat page refuses to load on unverified hostnames, preventing accidental exposure on staging or preview environments you did not approve.
  • Hosted chat can issue SSL for your custom domain with confidence that you control the DNS zone.

Verification paths: WooCommerce pairing or DNS TXT

There are two ways to verify a storefront domain. Pick the one that matches how your store is set up.

Verify with a DNS TXT record (step by step)

If you are not using the WooCommerce plugin, verification runs through a standard DNS TXT record. AgenticCart gives you the exact record name and value in the dashboard; you add it at your DNS provider and click Verify.

  1. 1

    Copy the TXT record from the dashboard

    AgenticCart shows both the host/name and the value. The value is a unique token that identifies your account, similar in shape to agenticcart-verify=abcd1234efgh5678.
  2. 2

    Add the record at your DNS provider

    Open your DNS provider (for example Cloudflare, Namecheap, Route 53, Gandi, OVH, GoDaddy) and create a new TXT record. The record type is TXT, the host is the one shown in the dashboard, and the value is the token — paste it exactly, without extra quotes.
  3. 3

    Wait for DNS propagation

    Some providers publish changes in minutes; others take longer. A public DNS checker can confirm whether the record is visible from the outside world yet.
  4. 4

    Click Verify in AgenticCart

    AgenticCart queries the public DNS for the expected value. The domain is marked as verified as soon as the record is visible.

For reference, a typical TXT record row at a DNS provider looks like this:

DNS TXT record (example)
Type   Host                         Value                                   TTL
TXT    @ (or yourbrand.com)         agenticcart-verify=abcd1234efgh5678     Auto

TIP

If your provider asks for a full host like yourbrand.com. with a trailing dot, copy the value AgenticCart shows and do not add extra characters. Extra quotes or trailing dots are the most common reason a verification check fails.

Subdomain and wildcard verification

If the AI sales agent will run on a subdomain such as chat.example.com, verify the exact hostname or use the wildcard option shown in the dashboard where available. The verified hostname should match where the hosted chat page is actually loaded — verifying example.com does not automatically cover chat.example.com unless you used the wildcard option.

Merchants with multiple storefronts, country-specific domains, or staging subdomains can add each domain separately. The dashboard keeps a list of every verified domain on the account so you can see at a glance what is approved.

What verification unlocks

  • Create and publish AI sales agents scoped to the verified domain.
  • Launch a hosted chat page on a subdomain you control.
  • Run multi-domain setups where your plan supports them — see plan limits.

Troubleshooting domain verification

  • Verification keeps failing — confirm the TXT value is copied exactly, saved on the right host, and not wrapped in extra quotes.
  • DNS looks correct but still fails — propagation can lag. Wait 10–30 minutes and try again; check a public DNS lookup tool to see what the world resolves.
  • Hosted chat says invalid origin — make sure the page hostname matches the verified domain or wildcard exactly, including the subdomain.
  • Multiple records on the same host — most DNS providers allow several TXT records on the same host; keep the AgenticCart record alongside existing ones (for example SPF) rather than replacing them.
  • You moved domains — add and verify the new domain before moving the AI sales agent. The old domain can stay verified until you remove it.

For broader issues, see the AgenticCart troubleshooting guide, and for the trust model behind verification, see security and trust.

Frequently asked questions

Why does AgenticCart require domain verification?
Verification prevents third parties from pointing the AgenticCart hosted chat at subdomains you do not control. It also lets AgenticCart issue SSL for your hosted chat domain safely, because DNS ownership is proven.
How long does a DNS TXT record take to propagate?
Usually minutes, sometimes longer. Provider TTL settings and intermediate DNS caches decide the delay. If the record is not visible after 30 minutes, double-check the host name and value — a typo is the most common cause.
Can one account verify multiple domains?
Yes, subject to plan limits. Add each storefront domain separately through the dashboard. Multi-domain merchants typically verify a root production domain plus any country-specific or campaign domains they use.
What happens to my agents if a domain stops verifying?
If the TXT record is removed or DNS stops answering, AgenticCart eventually flags the domain as unverified. The hosted chat page stops loading on that domain until you restore the record. Re-adding the record and clicking Verify brings it back.
Is domain verification the same thing as hosted chat DNS setup?
No. Verification is a TXT record that proves ownership. Hosted chat uses a CNAME (or A record) to route shopper traffic to AgenticCart's hosted chat infrastructure. A hosted chat domain still needs to belong to a verified domain. See hosted chat domain setup for the CNAME flow.

Next steps