Tag: AI Strategy

  • The Agent-Ready Site: What Kin’s WebMCP Launch Means for Every Business Website

    The Agent-Ready Site: What Kin’s WebMCP Launch Means for Every Business Website

    On October 23, 2026, Kin Insurance became the first U.S. home insurer to enable WebMCP in its quoting experience — an open web standard that lets an AI agent work directly with kin.com, so a homeowner can tell ChatGPT "help me shop for home insurance" and get back a real quote. Strip away the insurance details and what remains is a pattern every business website is about to be measured against: is your site built for the agent your customer sends?

    Most businesses are still arguing about whether to let agents in. Kin skipped that argument. The interesting question is what its launch is made of, layer by layer — because three of the four layers are already visible in our own fleet's numbers.

    Layer 1: Decide to welcome the machine

    Agent traffic is not coming; on our own sites it is already the majority — roughly 62% of visits across the fleet we run are bots and agents, not people. The only choice left is whether that traffic meets a door or a wall.

    Kin chose the door, publicly and in advance: it had already announced that AI shopping agents are welcome on kin.com rather than blocked, naming Meta's Muse among them. The opposite choice exists in the same industry — in September, insurance marketplace Insurify blocked Muse from its comparison platforms, arguing an agent could pull a price stripped of the context that makes it meaningful. Both are coherent positions. What is no longer available is having no position: a site that has not decided is a site whose default settings decide for it.

    Layer 2: Structure the content so a machine can carry it accurately

    An agent can only repeat what it can read, so the agent-ready site is built out of answers, not brochures: one real question per page, paragraphs that stand alone as complete ideas, and structured data underneath that states the facts in machine-readable form.

    This is the layer we work in every day, and it is unglamorous, mechanical work. Tonight, on one operator site in our fleet, we finished putting structured FAQ data — drawn from each page's own questions and answers, verbatim — onto 155 of its 166 articles, because agents cite what is structured and skip what is implied. Multiply that instinct across every page a business owns and you have the content layer of agent-readiness: nothing important lives only in an image, a video, or a sales conversation.

    Layer 3: Give the agent a way to act, not just to read

    WebMCP is the layer most sites do not have yet: the site declares the actions an agent may take — get a quote, with these inputs, in this order — so the agent executes a designed path instead of improvising clicks across a human interface.

    Kin's version is a quote flow, and its testing shows why the layer matters: agents reached a finished quote after asking the consumer only a handful of questions, because the path was declared and the carrier's data filled the rest. The equivalent for any business is the moment a visit becomes a transaction — a booking, a quote, an order. Our own commerce thinking already runs on two rails, one built for humans at a checkout and one an agent can complete; Kin just shipped the insurance version of the second rail, first.

    Layer 4: Measure what the machines do

    Agent-readiness you cannot measure is a vibe. Kin will know whether agents quote it, because the protocol makes agent sessions countable; the rest of us measure the read layer — which pages agents cite, which questions they bring, how the share moves.

    On tygartmedia.com, we track AI citations from our own search-engine exports rather than a vendor's estimate: 1,459,726 citations across 922 cited pages in the October 15 export, up from 269,399 across 324 pages in the September 27 export. Those numbers are the scoreboard for layers 1 and 2. The day an agent can transact here, layer 3 gets a scoreboard of its own.

    Where our fleet honestly sits

    Layers 1, 2, and 4 are running here today — welcome posture, structured content, citation measurement. Layer 3, declared agent actions, is what Kin shipped first, and it is the next build. That is a fair summary of most of the web right now: readable by agents, citable by agents, and still requiring a human to show up for the transaction itself.

    The businesses that treat that gap as a roadmap, rather than a surprise, are the ones whose sites will be ready when their customers stop browsing and start sending.

    Frequently asked questions

    What is WebMCP? An open web standard that lets an AI agent interact with a website through a machine-usable path the site itself declares — no plug-in and no screen-scraping. Kin enabled it in its home insurance quoting experience on October 23, 2026, the first U.S. home insurer to do so.

    What makes a website "agent-ready"? Four layers: a deliberate decision to welcome agent traffic instead of blocking it by default; content structured as standalone answers with machine-readable data underneath; a declared path that lets an agent complete an action, such as a quote or booking; and measurement of what agents actually do on the site.

    Do agents really visit business websites that much? On the fleet we operate, roughly 62% of visits are bots and agents. The share varies by site, but the direction does not: the reader a growing share of your pages serve first is a machine deciding what to show its human.

    Source: Kin Insurance announcement via PR Newswire, October 23, 2026. Fleet figures are Tygart Media's own: bot share from our site analytics; citation counts from our Bing AI Performance exports of September 27 and October 15, 2026.

  • AI Visibility: The LLM Optimization Strategies We Actually Run

    AI Visibility: The LLM Optimization Strategies We Actually Run

    Most LLM optimization advice is written by people who have never watched an engine decide whether to cite them. We have — monthly, in the engine’s own reports, across a small fleet of sites. What follows is not a theory of AI visibility. It is the playbook running on our sites right now: seven strategies, each with the number that proves it, each boring enough to actually compound. If a strategy can’t name the report that would show it working, it isn’t a strategy. It’s a hope with a webinar.

    1. One question per page, in the asker’s words

    An AI answer is assembled from pages that match the question being asked — so build pages that are the answer to one real question, titled the way a person actually asks it. Our certification guide for restoration contractors doesn’t chase “IICRC resources.” It answers what IICRC certification is, what it costs, and how to keep it current — and on Bing’s ledger we hold about a third of all citations for “what is iicrc certification” and 36% for “iicrc certification cost.” Nobody types marketing copy into an AI. They ask questions. The page that sounds like the answer wins the citation.

    2. Write paragraphs an engine can lift

    Citation is extraction. When an engine grounds an answer, it pulls the passage that stands on its own — the paragraph that contains the fact, the number, and the context in one self-contained block. So write that way on purpose: every paragraph a complete little model that still makes sense if it’s the only thing quoted. Buried facts, pronoun chains that need the paragraph above, and throat-clearing introductions are all invisible to an extractor. A page of liftable paragraphs beats a beautiful essay the engine can’t cut a piece from.

    3. Let the engine consolidate — then feed the winner

    Given two similar pages, an engine picks one and starves the other, and it shows you the execution in the reports. Our flagship certification page climbed four straight monthly exports — 1,635, then 1,913, then 2,454, then 2,790 citations — while its near-duplicate twin fell from 304 to 6. The strategy is to cooperate with that verdict: one page per topic, the cluster’s links pointed at the winner, old strays redirected to it. We spent part of today doing the plumbing version of this — three orphaned URLs that were leaking to our homepage now land on the pages that earned the citations. Fighting consolidation splits your authority. Feeding it compounds.

    4. Let the engine write your editorial calendar

    The most valuable document in AI visibility is free: the grounding-query report, which lists the actual questions your pages were pulled for — including ones you’re cited on weakly, and new ones appearing for the first time. That list, plus the topic opportunities the same dashboard surfaces, is a calendar written by demand instead of guesswork. This article exists because that report said people are asking how LLM optimization works. Half of what we publish starts as a line in an export. Guessing topics is a tax on people who won’t open a free report.

    5. Publish numbers nobody else has

    An engine cannot ground an answer on your competitor’s guess — but it can ground one on your data, if your data is the only place the number exists. First-party figures are the one content asset that can’t be copied by writing faster: your exports, your measurements, your before-and-afters. We print our own citation report card in public, limits included, and it keeps getting cited precisely because no one else can produce those numbers. Whatever your industry measures privately is a citation asset sitting in a drawer.

    6. Structure for extraction

    Give the machine clean handles: question-and-answer sections whose text matches the structured data behind them, tables with the real figures instead of ranges blurred into mush, section anchors a citation can point at. When we rebuilt our flagship page, we replaced three inconsistent blended price ranges with one fee table carrying the actual numbers — tuition, exam fee, renewal — each in the open where an extractor can take it. Vagueness feels safe to writers. To an engine, it’s just unusable.

    7. Be legible as an entity

    Agents do the first sort now — of vendors, of hires, of experts — and they sort on what your profiles actually say. We learned this watching a genuinely excellent operator get skipped by an automated screen because his headline was three abstract nouns and no signal. Your site, your company page, and your profiles should each state, in plain words, what you do, for whom, and where — written for the machine doing the first read and the human doing the second. If an agent can’t summarize you accurately in one sentence, your visibility strategy has a hole no content calendar will fill.

    The compounding is the strategy

    None of these moves trends. Each is a small, verifiable bet placed monthly against the engine’s own ledger — which is why measurement isn’t step eight, it’s the ground the other seven stand on; our tracking method is written up here, and the receipts we’d demand from anyone selling this work are in the buyer’s test. LLM optimization, done honestly, is a publishing discipline with a feedback loop — not a hack, not a plugin, not a score you buy. The engines are reading either way. The only choice is whether what they find is built to be cited.

  • How We Track Whether AI Cites Us

    How We Track Whether AI Cites Us

    Every week there is a new tool that promises to track your “AI visibility,” and most of them are selling a number they invented to a market that can’t check it. We track whether AI cites us for a living — a small fleet of sites, measured monthly — and our whole stack costs nothing. What it costs instead is discipline: knowing what each instrument actually measures, which cells in which reports lie, and which three numbers are worth your attention. This is the stack, the method, and the traps, from the reports we pulled today.

    Start with the engine’s own ledger

    Bing Webmaster Tools has an AI Performance section, it is free, and almost nobody in this business has opened it. It reports two things no third-party tool can know firsthand: the grounding queries — the actual questions for which Copilot and Bing’s AI answers pulled your pages as sources — and your citation share of each one. A third-party tracker samples AI answers from the outside and guesses. This is the engine’s own bookkeeping. If you do nothing else in this article, connect your site there and pull the two CSVs: AI Search Queries and AI Page Stats.

    Read the two reports against each other, because individually they will lie to you in specific, learnable ways. Today, a filtered export for one of our sites showed a grounding query with 2,796 citations and a citation share of 0.00% — an impossible pair. The page report for the same window showed our page taking 2,790 of those citations. The share cell in a filtered view was simply broken. The lesson is not “the data is junk.” The lesson is that a citation number is only as good as the second report that confirms it.

    The three numbers worth watching

    One: citation share on the queries that pay. Not total citations — share, on the handful of questions your buyers actually ask. Share is a rate over a trailing window, not a switch that flips, so judge it the way you’d judge a batting average: this month’s window against last month’s, same instrument, same site. A share that climbs two windows in a row is the engine changing its mind about you. A share that jumps once is weather.

    Two: the per-page trend. Page-level citations tell you where the engine is consolidating. Our certification page for restoration contractors climbed four straight exports — 1,635, then 1,913, then 2,454, then 2,790 citations — while its near-duplicate twin collapsed from 304 to 6. That is the engine picking a winner between two similar pages, in public, in numbers you can watch. When you see it, feed the winner: better structure, tighter answers, the cluster’s links pointed at it. When you see the split instead — two pages dividing one topic’s citations — you have found the leak.

    Three: new grounding queries. Every export contains questions you have never seen, some of which you are already being cited on without knowing it. Those are the cheapest wins in the whole system: the engine has already decided you are relevant; a page that answers the question directly, in the asker’s words, converts a toehold into a position. Half of what we publish starts as a line in this report.

    The second instrument: what people do after the click

    Microsoft Clarity is the other free half of the stack — session recordings, heatmaps, and an export API — and it answers the question citation reports can’t: what happened when the visitor arrived. Its limits are just as instructive. Clarity masks typed text by design, so a search box can light up with clicks while the actual search terms never appear in a recording. We learned to read the terms out of the URLs instead — a completed site search carries its query in the address — and when we pulled three days of URLs across two sites this week, we found a search box that had drawn 69 clicks and zero completed searches. The box was being touched constantly and used never. No dashboard said that. Two exports and ten minutes of reading did.

    Clarity also ships AI summaries of your traffic, and our rule for those is blunt: a summary is a lead, never a fact. Session counts and page claims get settled by the raw export or a live fetch, because the one time it matters is the one time the summary will be confidently wrong. Treat every AI-written summary of your own analytics the way you’d treat an AI-written summary of anything: as a rumor with good formatting.

    What the paid trackers add — and what none of them can see

    Paid visibility trackers earn their money on breadth: they run panels of prompts against ChatGPT, Claude, Perplexity, and Google’s AI surfaces, where Bing’s report covers only its own family. If your buyers live on those engines, a panel tool tells you things the ledger can’t. Buy breadth if you need it. But understand what you’re holding: a sample of answers, taken at a moment, from accounts and locations that may not match your buyers. It is a poll, not a census. The engine’s own report is the census for its engine — narrower, and exact.

    What no tool in this category can see is your side of the wall: which pages your own visitors touch, what they search for on your site and fail to find, which of your URLs the bots are actually crawling. Roughly six in ten visits across our fleet this month were automated, and that share climbs every month. Any visibility number that doesn’t ask “of the humans or of the machines?” is averaging two different worlds into a fiction. Your own logs and exports are the only place that question gets an honest answer.

    The tool categories, compared honestly

    Search for answer engine optimization tracking tools and you will find four kinds of instrument wearing the same label. Engine-native ledgers — Bing Webmaster’s AI Performance reports are the working example — show the grounding queries and citation shares from inside one engine family: narrow, exact, free. Behavior analytics like Microsoft Clarity show what visitors did after the click: also free, also first-party, blind to anything that happens off your site. Paid panel trackers run batteries of prompts against ChatGPT, Claude, Perplexity, and Google’s AI surfaces and report how often you appear: broad, sampled, and only as representative as their prompt list and accounts. Your own server logs and exports are the unglamorous fourth category, and the only one that separates human visits from the bot traffic that now makes up the majority of most sites’ requests.

    None of the four replaces another, and the marketing of each pretends otherwise. The ledger can’t see ChatGPT. The panel can’t see your visitors. The analytics can’t see the citation that never became a click. A working stack layers them in that order — ledger first because it’s ground truth for its engine, analytics second because behavior is where money is made, panels third if your buyers live on engines the ledger doesn’t cover, and your own logs underneath everything as the lie detector. Anyone selling you a single tool as the whole answer is selling the tool, not the answer.

    The discipline is the product

    The stack is two free Microsoft tools and a spreadsheet habit. The method is: same reports, same window, read against each other, three numbers, every month, and a standing suspicion of any figure that arrives without a second source. None of that is purchasable, which is exactly why the tools market would rather sell you a score.

    Skip the score. Pull your grounding queries. Find the page the engine is consolidating onto and the twin it is starving. Read your new questions like a suggestion box written by the market itself. That is tracking AI visibility — not watching a gauge, but reading the engine’s mail. It has been sitting in a free dashboard the whole time.

  • The Shortlist Is Written by a Machine Now

    The Shortlist Is Written by a Machine Now

    Somewhere tonight, a business owner is going to ask an AI assistant a question like “top ai seo agencies” or “top ai seo services for small businesses” — and the assistant is going to hand back a shortlist. Nobody at those agencies will be in the room. Nobody will make a pitch. The machine will build the list out of what it can find, cite, and trust, and most of the owners reading it will never ask how the list got made.

    We know these questions are being asked, because the search engines publish the opportunity data. In Bing’s own topic reporting for our site, that cluster of buyer questions — “top ai seo agencies ai-driven services,” “top rated ai seo services for small businesses,” “affordable aeo services strong seo results” — shows up as live demand, month after month. People are hiring this way now. So the only question that matters for a buyer is: what is the machine actually reading when it decides who makes the list?

    The shortlist is built from citations, not claims

    An AI assistant recommends what it can ground. When it answers “who should I hire,” it leans on pages it has cited before — pages whose facts it has already used in other answers. An agency’s beautiful website copy about itself barely registers. What registers is the agency’s citation footprint: how often its pages are used as sources, on which questions, and whether that number is climbing or flat.

    That flips the buyer’s job. You are no longer comparing pitch decks. You are reading report cards — and the agency selling AI visibility has one whether it shows you or not. So ask for it. Any agency doing this work seriously can pull its own numbers from Bing Webmaster’s AI Performance reports in about five minutes. If they have never looked at them, you have learned the most important thing on the call.

    The receipts test: four things to ask for

    One: total AI citations, and the trend. A single big number means little; a number that climbs month over month means the engine keeps choosing their pages. Ask for this month against last month, from the report, not from a slide.

    Two: the grounding queries they win. The report lists the actual questions their pages get cited on, with their share of each. An agency cited on the questions its buyers ask is proving something. An agency cited on a mountain of questions nobody in its market asks is farming trivia.

    Three: one page that climbed, and why. A single page’s citation history is a story with a mechanism — consolidation, structure, freshness, a topic the engine needed. If they can tell you that story with numbers, they understand the machine. If they can’t, their results, if any, are weather.

    Four: what they measure every month. Citation visibility is a trailing measure — a rate over the last thirty days, not a switch that flips. An agency that reports it that way, and can show you the rate moving, is measuring the real thing. An agency that promises rankings by Friday is selling the old world at new prices.

    Our own report card, printed in full

    We will go first, because that’s the test. From our own Bing Webmaster AI Performance exports — the same reports any agency can pull — tygartmedia.com was cited 1,459,726 times across 922 pages in the most recent full export on file (October 15, 2026). On the question “claude pricing,” our pages hold a 24.5% citation share; on “anthropic console,” 54.5%. That is the top of our footprint, and it is mostly content about AI tools and pricing — the audience that reads this site.

    The number we watch hardest is smaller and closer to our trade. Our page on IICRC certification for restoration contractors — the credential page for the industry we serve — has climbed four straight exports: 1,635 citations, then 1,913, then 2,454, then 2,790 (September 27 through October 24). A near-duplicate twin of that page collapsed over the same stretch, from 304 citations to 6, because the engine consolidated onto the stronger page. We didn’t game that. We watched it in the data, understood it, and fed the winner.

    What our numbers don’t show, said plainly: these are Bing and Copilot figures. Google’s map is different, every engine’s is, and anyone who quotes you one engine’s numbers as “AI visibility” full stop is rounding in their own favor. Citation share also trails the work by weeks — it is evidence about the recent past, not a promise about your future. And a footprint proves an agency can get itself cited; whether it can do it in your vertical is a separate question, which is why item two of the test — the grounding queries — matters more than the total.

    The buyer’s move

    The machine is going to keep writing the shortlists. That part is settled. What isn’t settled is who is on them, and the way onto the list is not a better sales page — it is a body of work the engines already trust enough to cite.

    So if you are hiring: skip the deck, ask for the report. Total citations and the trend. The grounding queries and the shares. One page that climbed and the story behind it. The monthly measurement, in the trailing-rate language of people who actually watch it. An agency that can hand you those four things is showing you its own exhaust — the work, on tape. An agency that can’t is asking you to take its word for the one thing it claims to sell.

    Take nobody’s word. Ours included. The reports are free, they take five minutes to pull, and they do not care whose logo is on the website. That is exactly why they are worth reading.

  • The First Agent You Hire Answers the Phone

    The First Agent You Hire Answers the Phone

    Nobody’s first AI hire is a strategist. Ask a room full of operators what they’d hand off first and nobody says the thinking — they say the phone. The call that comes in at 6:40, after the office went dark at five. The form filled out at midnight, water coming through the kitchen ceiling. The lead that goes to whichever company answers first — and in home services, the first answer is very often the whole sale.

    That seat — first response — is where small businesses are actually hiring agents, and the money just said so out loud. On October 13, Dapta, an AI sales agent company out of Scottsdale and Miami, announced a $6 million seed round led by Chingona Ventures. Its agent, Dapti, answers, qualifies, and books the meeting the moment a prospect reaches out — no human touching it. Dapta says 200,000-plus users are on it, signing up at better than 4,000 a week, and that revenue will pass $4 million this year. Home services is one of the verticals where it took hold first.

    The seat, in a real shop

    First response in a small shop is a person-shaped hole. The owner answers between jobs, one glove off. The office manager answers until five. After five, a service answers, or nobody does, and the prospect — wet floor, search results page in hand — calls the next name on the list. It’s a staffing problem, not a marketing problem — one that shows up at the exact hours nobody wants to staff.

    The money makes it worse. On Google Local Services, a connected call that runs past twenty seconds can bill you whether a person picked up or not — you pay for the ring. And the caller isn’t comparison-shopping at leisure. They’re standing in water, or sleeping in a 90-degree house, and they hire the first competent voice that treats them like a person.

    What the agent can own outright

    The front half of the seat is script work, and script work is exactly what an agent is for. Answer instantly, at any hour, in the customer’s own language — Dapta got its start with Spanish-speaking owners in the U.S., and first response is meeting the customer where they are. Ask the basic qualifying set: what happened, where is it, when did it start, who is paying, how do we reach you. Then do what most shops fumble even in business hours: put a real appointment on a real calendar, confirmed where the customer can see it — not a callback promise the morning forgets.

    None of that requires judgment — just the script, the calendar, and the discipline to run both at 2 a.m. the way they run at 10 a.m., on the nights the office sits empty.

    What the human keeps

    Qualification questions are not qualification judgment, and the difference is the entire ballgame. The questions collect facts. The judgment decides what the facts mean: Is this a job we want — at this size, this distance, for this payer, with the crews already buried? A flooded kitchen ten minutes away and a “come look at a stain” forty minutes out both answer the questions perfectly. Only one of them should get your Saturday.

    The human also keeps pricing, promises, and the handoff. What a job costs is a person’s call, made with the board in front of them. “We’ll have a crew there by nine” is a promise only someone who knows the crew should make. And the moment a prospect stops being a lead and starts being a customer — when they need to hear a real person owns their problem — a person takes the conversation. The agent’s job is to make that moment arrive fast, facts collected and appointment real. It is not to be that moment.

    The failure shape

    Hand an agent the whole seat — the questions and the judgment both — and it will qualify everybody. It will book the estimate outside your service area because nothing told it distance matters. It will fill the calendar with meetings a person would have filtered in thirty seconds — and once your techs learn to distrust anything the system books, you have automated the exact problem you bought it to solve. The bad version doesn’t fail loudly. It fails as a slow leak — wasted drive time, stood-up appointments — until somebody turns it off and announces that AI doesn’t work.

    The seat works when its boundary is drawn, not when the model is smart. A boundary is a list: what it can ask, what it can book, what it can never promise, and where it stops and hands over. Dapta’s own framing stops at answer, qualify, schedule — first response, not the close. That is not a limitation. That is the product, correctly shaped.

    Hire it like a person

    You would never hand a new receptionist the phone on day one with no script, no boundary, and no “if it’s this, come get me.” An agent seat deserves the same three things, because it is the same hire: a script it runs word for word, a boundary it does not cross on its best day, and an escalation path that puts a human in the conversation the moment judgment enters.

    The $6 million is a bet that every small business staffs this seat the way it eventually got a website. The operators who get it right will not be the ones with the smartest agent. They will be the ones who wrote the seat down — job, boundary, and the name of the human who owns the judgment — before they let anything answer their phone.

    Sources: “Dapta Raises $6M to Accelerate the Adoption of AI Sales Agents for SMBs across the U.S. and Latin America,” Dapta LLC via GlobeNewswire, October 13, 2026 — globenewswire.com. User, signup-rate, and revenue figures are Dapta’s own statements in that release.

  • They Say GEO Isn’t Real. Watch a Website Answer Questions About Itself.

    They Say GEO Isn’t Real. Watch a Website Answer Questions About Itself.

    People keep telling me AEO and GEO are the new snake oil. Acronyms invented to sell audits. “SEO is SEO,” they say, “and the rest is conference talk.”

    Fine. Let me show you the thing itself, on a site I run, with nobody’s hands on the scale.

    What you’re watching

    That’s Healthcare Facility Hub — a site for people who run hospital facilities. In the corner of every page sits an AI that knows one thing: the site itself. It’s trained on the site’s own content and nothing else. No open internet. No general model knowledge doing the heavy lifting. If the answer isn’t in the site’s pages, the AI doesn’t have it.

    I spent five minutes asking it questions on camera. Three things happened, and they’re the whole argument.

    First: it answers like the content is a database

    Ask it what an infection control risk assessment requires and it doesn’t write an essay. It returns the site’s own material as structure — the risk classes, the types, and then, when I push on negative air pressure, the actual working numbers: the target pressure, the alarm setpoints, the HEPA specs a facilities team would use on a job.

    That’s not a chatbot being clever. That’s what happens when every page is built as a clean, standalone record — one question, one complete answer, the facts in the open — instead of a pile of marketing prose with keywords folded in. The AI can pull from it because the page was built to be pulled from.

    Second: ask it something the site doesn’t have, and it says so

    I asked it for stories about Chicago. It said: we don’t have any content or stories about Chicago in our current site resources.

    Sit with that for a second. The big chatbots, asked the same question, would give you Chicago stories — real, invented, blended, who knows. This one refused, because its world ends at the edge of the site’s content, and it knows where the edge is.

    That’s not a limitation of the demo. That IS the demo. An answer engine is only ever as good as the corpus it can draw on. When the corpus is disciplined, the answers are disciplined. When there’s nothing there, an honest system says nothing’s there — and a visitor, or an engine deciding what to cite, can trust everything it did say.

    Third: the answer ends at an asset

    Follow the thread to the end of the video and I’m not reading a blog post. I’m opening a one-page field sheet — the article distilled into a printable PDF with a QR code, made to be carried onto a hospital job site.

    That’s the shape of the whole thing. A question gets asked. The structured content answers it. The answer hands you something usable. Search used to end at a blue link and a hope. This ends at a tool in a facility manager’s hand.

    Why this is what the engines are doing to you

    ChatGPT, Perplexity, Copilot, Google’s AI — different companies, same basic move. They read corpora, they extract answers, they cite the sources that could answer. Your website is either a corpus they can extract from, or it’s a brochure they skim past on the way to somebody else’s.

    We measure this instead of arguing about it. We run a fixed battery of questions a buyer would actually ask, score what our sites’ AI answers from their own content, and log where it has nothing — those gaps become the next pages we write. This morning, on a sibling site in a different industry, that battery came back 24 passes out of 36, with the misses itemized as a content list. The scoreboard is not a vibe. It’s a work queue.

    And the citation side gets measured too — which engines cite which sites, on which questions, over a trailing thirty days. When the numbers move, we know why, because we know what we published and what it answered.

    The part nobody wants to hear

    None of this is a trick you bolt onto an existing site. The AI on that page answers well because the site underneath it was rebuilt to be a knowledge base — treated like a headless database that happens to have pages attached. Every article answers one real question, in the words the asker would use, with the numbers in the text where an extractor can find them.

    If an AI trained only on your own website can’t answer your customers’ questions, the big engines can’t either. They’ll answer from a competitor whose site can. That’s not a threat I’m selling. It’s arithmetic you can run on your own site this afternoon — most sites have a chat box or a search bar you can interrogate. Ask it your customers’ five best questions. Count what it actually knows.

    We already know how that count comes out for most sites. It’s why the phone rings here.

    The recording is unedited screen capture from healthcarefacilityhub.org, October 22, 2026 — the site’s own AI, its own content, my own questions. Narration on the video is Glint, my AI. This is the work, on tape.

    Download this article as a PDF

    Run the count on your own site

    The AI Citation Quick-Scan asks ten homeowner prompts — the questions your buyers actually put to ChatGPT, Perplexity, and Copilot — and shows you whether your business is the answer, and if not, who is. It is the same interrogation I ran on camera, pointed at your market: the AI Citation Quick-Scan, $97 — and the $97 comes off the package price if you move forward.

  • Wonder Full Stays in the Seat. The API Key Is a Different Promise.

    Wonder Full Stays in the Seat. The API Key Is a Different Promise.

    On October 12, 2026, Meta launched two models that share a name and almost nothing else. Muse Wonder is a product you can call: it sits on the Meta Model API at $4.00 input, $0.20 cached input, and $20.00 output per million tokens, and inside Muse Code. Muse Wonder Full is a model you can only sit in front of: it exists exclusively inside a Muse Code subscription, on the Power Usage and Maximum Usage plans. The decision an operator makes before pointing either one at a real repository is not which model is smarter. It is which promise they are buying — and the seat’s default promise is not the one most buyers think they made.

    The frontier model is a seat, not a SKU

    Meta’s own availability table is the whole story in four cells. Muse Wonder (muse-wonder-1.0): available on the Model API, standard mode only, and in Muse Code on pay-as-you-go and every plan. Muse Wonder Full: not available on the API at all — Power Usage and Maximum Usage subscriptions only.

    There is no back door. Setting reasoning effort to “max” on muse-wonder-1.0 does not select Wonder Full; Meta’s models page says so in plain words. Meta publishes no API model ID for Full. A team that wants Full behind its own product has, in the words of one launch-week review, no path at any price — businesses can test it inside Meta’s coding environment and cannot deploy it through the standard API.

    The seat prices are printed on the Muse Code product page: Everyday Usage $5 a month, High Usage $15 at 5× the Everyday allowance, Power Usage $50 at 20×, Maximum Usage $200 at 80×. Power is the cheapest chair that includes Wonder Full. The allowances run on five-hour and weekly resets, and per the Terms, a subscription’s per-period allowance expires at the end of each period and does not roll over. On Maximum, when the allowance is gone, Meta’s documented way forward is to wait for the refresh.

    The credential is a leash

    The subscription applies to the API key Meta automatically connects during Muse Code CLI onboarding, and the subscriptions doc is explicit about the boundary: “This credential is for use with Muse Code only.” The Terms give the arrangement its legal name — a Coding Harness Subscription — and the same restriction: the connected key “may not be used to access the Services outside the coding harness or to circumvent your subscription’s usage limits or billing.”

    Any additional API keys you create under the same account are billed pay-as-you-go, per token. So one Meta account holds two different commercial relationships at once: a flat seat that works only inside one CLI, and metered keys that work anywhere except that they can never call the frontier model. Budget them as two products, because Meta does.

    The default is the decision

    Here is the trap, and it is set by a default. “Muse Code subscriptions default to Contributor mode. In Contributor mode, you get more usage from your plan in exchange for letting Meta use your content — the prompts, code, files, and context you send, plus the model responses you get back — to train future Meta models.”

    A careful buyer can still walk into it. Meta’s Model Designation Policy lists Muse Wonder and Muse Wonder Full as Standard Models — the tier whose use constitutes Standard Services, where content is not used for training. The same policy then overrides the list: “If you access the Services through a Coding Harness Subscription, you are considered to be using the Contributor Services by default regardless of which Meta Model you select.” Terms section 3.3 says the same. In Muse Code, Contributor mode is not a model name. It is a subscription setting, and it is on.

    Turning it off is one toggle: open /settings in Muse Code. The help page states what the toggle does and does not do: “Turning Contributor mode off changes how much usage you get from your plan. It doesn’t change which plan you’re on.” How much usage changes, Meta does not publish — no ratio, no prompt count, no price difference appears in the documents. The honest line for a budget is that the size of the privacy discount is undocumented.

    Meta’s own warning belongs in every seat-setup checklist, quoted exactly: “You must not submit sensitive, confidential, or personal information to the Discounted Services. If your use case involves processing personal information, please use Standard Services.” Accounts with Zero Data Retention cannot use Contributor mode at all — and ZDR itself is an organization-level enablement Meta’s sales team turns on for Model API accounts, not a toggle in the CLI, and it does not cover requests made with a personal account.

    The switch does not reach backward

    The off-switch is prospective. Terms section 3.3: a change to Standard applies “prospectively only; it would not apply to Content previously submitted to the Contributor Services, and Meta’s rights with respect to that Content under Section 6 will survive the change.” Everything a seat sent while the default was on stays under the training grant after you flip the setting.

    Section 6.1 adds the subtler pull: “Content previously submitted to the Standard Services becomes Content submitted to the Contributor Services if it is included in any request to the Contributor Services, whether directly or as context or background for your prompts or instructions.” One later Contributor-mode session that pulls an earlier, clean conversation in as context reclassifies that content.

    The commitments page softens the arrangement with a safeguard and then qualifies it: before using Discounted Services content to train models, Meta “takes steps designed to disassociate that Content from your Accounts” — but Meta may use the same content for “evaluation, safety, abuse, quality, and policy review” without first applying those steps. And section 6.1 acknowledges the output side: models trained on your content may produce outputs “similar or identical to your Content,” including for third parties.

    The API shelf is labeled honestly

    On the API, the same choice exists — as a separate model name, printed on the pricing page where a buyer can see it. Contributor mode “isn’t available for Muse Wonder on Model API.” For Spark it is a different SKU: muse-spark-1.3-contributor and muse-spark-1.2-contributor at $0.10 input, $0.002 cached, $0.20 output per million tokens, against standard Spark at $1.25 / $0.15 / $4.25 — capped at 150 requests per minute against 3,000 for the standard IDs. The Muse Code product page labels the two rows without euphemism: the Contributor row is “Used to improve our products”; the standard row is “Not used to improve our products.”

    That is the contrast the seat hides. On the API, training is a priced, named, rate-limited variant a buyer selects on purpose. In the subscription, it is the factory setting of the harness — and the model table’s “Standard Model” label will tell a skimming buyer exactly the wrong story about which arrangement they are in.

    The operator’s checklist

    Decide the data arrangement before the repository, not after the first session. A public demo and a confidential codebase can run through the same agent on the same afternoon; they require different settings, and the setting is per-subscription, not per-conversation.

    Turn Contributor mode off in /settings before any client code, customer data, or contract-confidential material enters the seat — remembering that the flip protects only what is sent afterward, and that earlier standard content follows it if it is ever pulled back in as context.

    Buy the seat for the seat’s work. Wonder Full is a genuinely frontier tool for a person at a keyboard, and it is not a component. Anything your own product must call belongs on the API, in Standard mode, on keys you budget per token.

    This desk tracks Meta’s platform as it changes; the full rate card and the contributor tier’s arithmetic are in Meta Model API Pricing & Limits, and every Meta piece hangs off the Meta AI desk hub. The short version to tape above the desk: the model in the seat is not the model on the shelf, and the seat’s most consequential setting is the one nobody remembers choosing.

  • Six in Seven AI Answers Never Look Anything Up

    Six in Seven AI Answers Never Look Anything Up

    Most of what an AI answer says about your business was never looked up. It was remembered — or invented in the shape of a memory. Ahrefs put a number on that in a study published October 12, 2026: across 66.6 million free, logged-out ChatGPT responses from August and September 2026, a web search ran in only 14.4% of them. Six in seven answers were written without checking anything.

    That single fact reorganizes the work. If the answer usually comes from what the model already carries, then being findable is only half the game. The other half is being known — and, for the one answer in seven where the engine does go looking, having the fact it needs sitting in plain text on your own domain, where it looks first.

    The search, when it happens, is narrow

    The same study logged 15 million fan-out queries — the searches ChatGPT issues behind an answer when it decides to search at all. A searching response ran about 1.6 of them on average. This is not a research department fanning out across the open web. It is a quick, targeted check, and the targeting is the story.

    6.8% of those fan-out queries used a site: operator to search one specific website, spread across roughly 116,000 domains. Among the most common of those targeted searches, 75.9% pointed at a brand’s own site — not a retailer, not a forum, not a review aggregator. When the engine wants a price or a specification, it goes to the company that sells the thing.

    The vocabulary inside the queries leans the same way. The word “official” appeared in 13.1% of English fan-out queries in September 2026, up from 10.1% in August. “Price” climbed from 6.04% to 8.88% of fan-outs in the same month — a relative rise of nearly half. The engine is increasingly searching for the authoritative version of a fact, and the facts it most wants are commercial ones: what it costs, what it includes, what the official page says.

    Facts go home; comparisons wander

    Ahrefs paired the fan-out data with a separate test of 20,000 US prompts, and the split inside it is worth keeping separate in your head, because it is a different instrument from the 66.6 million. In that test, 84.4% of factual questions — pricing, product features, company details — cited at least one official source. For factual questions, 63.4% of all citations pointed at official websites. For comparison questions (“A vs B,” “which is cheaper”), the official share fell to 46.4%: most citations went somewhere else.

    Read together, the two datasets describe one behavior with two modes. Asked for a fact, the engine goes home to the source. Asked to judge, it goes out to the crowd. An operator cannot control the judging mode. The fact mode is entirely winnable: it is won by having the fact, in the open, on the domain the engine already searches by name.

    The playbook that follows

    Publish the price, the spec, and the support fact in plain text on your own domain. Not in a PDF the crawler has to excavate, not inside a configurator, not implied by a sales page’s adjectives. The fan-out query literally contains the words “official” and “price” — it is asking for a page that states the number. Whoever states it cleanly gets cited for it.

    Publish the pages only you can publish. Your measured results, your actual process, your own numbers with dates on them. A summary of somebody else’s facts competes with the original; the original is what the engine is learning to prefer (the citation movement below shows how far that preference has already moved).

    Treat fan-out queries as an instrument of their own. The queries an engine issues about your category — which words it adds, which domains it targets, how that shifts month to month — are a measurement channel separate from citation counts. Watch them separately. We grade the flight recorder, not just the answer, for the same reason: the queries show the intent; the answer only shows the outcome.

    Never blend two dashboards into one story. The 14.4% comes from 66.6 million free logged-out responses. The 84.4% comes from a different, 20,000-prompt test. The citation movements in the next section come from a third cut again. Each number is true inside its own denominator and misleading outside it. This is the same discipline we run on our own visibility work: being cited is not being chosen, and being measured is not being measured the same way twice. Our running instrument for the citation side is the Citation Pulse.

    The second movement: summarizers are losing

    Ahrefs’ Brand Radar citation data for the US — 2.4 million ChatGPT answers in March 2026 against 3.8 million in September, a different dataset from the fan-out study above — shows where the citations went. Reddit fell from roughly one citation in every five answers in March to about one in 43 by late September. Wikipedia fell from one in seven to one in 35. The share those summarizers and forums lost moved to research bodies, regulators, brand and support pages, and hands-on testers. On a matched set of about 25,000 prompts present in both months, every tracked site moved in the same direction, so the shift is not an artifact of new questions entering the sample.

    For an operator, that is the durable part of the whole study. The memory answers reward whoever the model already knows. The searching answers reward whoever publishes the primary fact. The citation trend rewards the originator over the summarizer. All three roads end at the same address: your own domain, carrying your own facts, in plain text.

    The same citation movement, read for hospitals and the firms that build for them — why clinical and facility specifications now have to live as primary documents — is on Healthcare Facility Hub: The Citation List Is Moving Toward the Source Document.

    Sources: Ahrefs, “How ChatGPT Does Query Fan-Out” (October 12, 2026) — fan-out dataset (66.6M responses, 15M queries, Aug–Sep 2026), the 20,000-prompt official-source test reported in the same article, and the Brand Radar US citation comparison (2.4M answers March 2026; 3.8M September 2026). Each figure above is stated with the dataset it came from; the three are not interchangeable.

  • Meta Model API Pricing & Limits: Wonder, Spark, and the Cheap Tier That Trains on You

    Meta Model API Pricing & Limits: Wonder, Spark, and the Cheap Tier That Trains on You

    From the Tygart Media Meta desk. Prices below are Meta’s published rates, verified against Meta’s own pricing documentation on October 13, 2026, and cross-checked against our account’s live catalog on October 19, 2026. This page is the desk’s drift-watch surface: when Meta moves a number, this page is where the change gets recorded, dated. Desk home: Meta AI, Run in the Open.

    Meta’s pricing has one genuinely simple story and one trap. The simple story: a flagship priced exactly at the market’s flagship rate, a workhorse priced like a workhorse, both with million-token context and no long-context surcharge. The trap is a third tier that costs about 95% less — because you’re paying with your data instead. Here is the whole map, with the trap labeled.

    The API tiers (per million tokens)

    Model Input Cached input Output Rate limits (per team)
    Muse Wonder $4.00 $0.20 $20.00 3,000 RPM / 4M TPM
    Muse Spark 1.3 / 1.2 / 1.1 (Standard) $1.25 $0.15 $4.25 3,000 RPM / 4M TPM
    Muse Spark Contributor $0.10 $0.002 $0.20 150 RPM / 3M TPM

    Wonder’s $4/$20 matches the going flagship rate dollar for dollar — Meta is not discounting its best model, it’s daring you to compare it. Spark at $1.25/$4.25 is the tier a working shop will actually live on: a quarter of the flagship’s input price and under a quarter of its output price, with the same 1M-token context window and the same rate limits. There is no long-context premium at any length, which quietly removes a whole category of surprise bill. Web-search grounding, if you use Meta’s built-in tool, is $2.50 per 1,000 queries on top.

    The rest of the catalog is priced like utilities: Muse Image generates at a flat $0.01 an image, Voice Transcribe runs $0.18 per audio hour with diarization, and the SAM 3.1 segmentation model is $2.50 per 1,000 images — all three confirmed in our own account census on October 14, 2026. Spark’s maximum output is 131,072 tokens; Wonder’s maximum output is not stated on the pages Meta publishes, and this page won’t guess it.

    The Contributor trap: cheap because it trains on you

    Read the Contributor tier’s price again: $0.10 in, $0.20 out. That is not a sale. Meta’s own pricing page is plain about the exchange — in Contributor mode, Meta may use your prompts and the model’s completions to improve and train its products. Your discount is paid in data. Standard mode, at the prices in the table above, is the mode where your content is not used for training.

    Our house rule, printed so our future selves can’t negotiate with it: Contributor tiers are for disposable experiments only — never for client work, never for unpublished material, never for anything you wouldn’t read aloud in Meta’s lobby. The arithmetic isn’t close. A shop that routes real work through Contributor to save $4 a million tokens is selling its clients’ material at a price it would never accept in a contract. And one more wrinkle worth knowing: Muse Code subscriptions default to Contributor mode unless you turn it off — so the trap is also a default, and defaults are where shops actually live.

    The Cursor split: Spark is in, Wonder is out

    If your shop runs Cursor, your Meta options today are exactly one model long. Muse Spark 1.3 is a first-class Cursor model — added September 8, 2026, about six days after the model itself shipped — at the same $1.25/$4.25 rates, with full access to Cursor’s agent tools, a 300k context window by default or the full 1M in Max Mode. Muse Wonder is not in Cursor at all: no model page, no changelog entry, no announced timeline, and Cursor’s official bring-your-own-key program covers five providers — Meta is not among them. The base-URL override workaround exists, but Cursor staff describe it as unsupported and partially broken, it applies globally while it’s on, and it can never bring you Wonder Full. Bottom line from a shop that checked: for Meta inside Cursor, run native Spark 1.3; for Wonder, use the API.

    Muse Code plans — reported, not verified by us

    Meta’s own terminal agent, Muse Code, is sold by subscription as an alternative to per-token billing. The plan structure is verified on Meta’s documentation: four tiers — Everyday, High, Power, Maximum — with Power and Maximum including Wonder Full, the stronger flagship variant that the API does not sell at any price. The dollar figures below come from secondary reproductions of Meta’s pages, and we label them reported because we have not paid one yet: Everyday $5/month, High $15/month (5×), Power $50/month (20×), Maximum $200/month (80×). When this shop runs Muse Code through a real sitting, this section gets rewritten from receipts. Until then, it stays labeled.

    What the numbers don’t tell you

    Two costs never appear on a pricing page. The first is token hunger: independent launch-week measurement found Wonder slower to first token than its rivals’ median and thirstier with output tokens, and in an agent loop — where a model may be called hundreds of times on one job — a thirsty model at a fair per-token price can still be the expensive seat. The second is your own switching cost, which Meta has unusually lowered: one key speaking OpenAI and Anthropic protocols means the harness you already run is the harness you evaluate with. Our proof of that, and the gotcha that came with it, is in The Meta Model API, As We Run It.

    Last verified: October 19, 2026. The desk’s catalog watch re-reads Meta’s model list daily; pricing drift gets recorded here with its date, the same discipline this site applies to Claude’s pricing.

  • The Meta Model API, As We Run It

    The Meta Model API, As We Run It

    From the Tygart Media Meta desk — our own API key, our own test envelope, our own receipts. Desk home: Meta AI, Run in the Open.

    Every vendor will sell you an API with a launch post. What a working shop needs is duller and more valuable: does it answer, does it finish real work, what does it cost to find out, and what stupid thing will eat your first afternoon? On October 14, 2026, we wired Meta’s Model API into our own tooling and ran it. Here is the whole story, including the part where we blamed the API for our own mistake.

    The setup: one key, stored like it matters

    Meta’s developer platform is dev.meta.ai. You make a key in the dashboard, you put it in a vault — ours lives in our credential store, injected into the process only at run time, never written to disk, never pasted into a chat. Billing rides a partner-controlled card with a hard $25 test envelope on it. That envelope is a deliberate choice: a new platform earns production trust in stages, and stage one is “prove it works for pocket change.”

    The first check cost nothing: list the models. Our key read Meta’s catalog clean — nine models, from Muse Wonder down to a segmentation model we still haven’t touched. A key that can read the catalog is a key that works; everything after that is about the work, not the wiring.

    The proof: a work-order-shaped task, 52 seconds

    We pointed OpenCode — an open-source terminal agent, version 1.19.0 — at Meta’s API as an OpenAI-compatible provider, and handed Muse Spark 1.3 the kind of job this shop hands every seat: a written spec (SPEC.md), from which it had to produce a working Python module (a slug utility) plus a pytest suite covering it. Not a riddle, not a benchmark — a small, real, verifiable unit of work with a pass/fail at the end.

    Spark 1.3 finished in about 52 seconds. Mid-run it discovered pytest wasn’t installed in its environment, provisioned its own virtual environment, installed what it needed, and ran its tests: 8 of 8 passing. Then we did what we do with every seat’s output, including our own: we didn’t take its word. We re-ran the suite ourselves, added five extra cases of our own, read the code line by line. All green, code clean. Total damage to the $25 envelope across the entire day’s probing of every text model on the account: under two cents.

    The gotcha: our first failure was not Meta’s

    The first attempt “failed.” Silently. No error, no output — the run simply never came back. The natural conclusion is that the shiny new API is broken. The actual cause: opencode run hangs forever when its standard input is left open in a non-terminal session. Run it with stdin closed — </dev/null — and it works perfectly. No API fault, no key fault; a harness quirk that cost us one debugging cycle and taught us, again, the oldest lesson in this shop: when a new platform “fails,” check your own plumbing before you write the platform off. We’re printing the gotcha in the desk’s first article on purpose. The next shop that wires this API deserves to skip our lost afternoon.

    One API, three dialects — and why a shop should care

    The most consequential thing about Meta’s API is not any single model. It’s that the same key speaks three protocols: OpenAI’s Chat Completions, OpenAI’s Responses API, and Anthropic’s Messages API. Meta’s own quickstart documents pointing Claude Code at api.meta.ai by changing a base URL, Codex at the Responses surface, and OpenCode at the OpenAI-compatible endpoint — all with the one key.

    For a shop, that collapses a real cost. Harnesses are habits: your prompts, your permissions, your work-order formats, your muscle memory. A model provider that demands a new harness taxes every one of those. A provider that plugs into the harness you already run lets you spend your evaluation budget on the only question that matters — is the model any good at your work? It’s also a discipline on the provider: when switching is cheap, the model has to win on merit every month, not on lock-in. We like platforms that volunteer for that test.

    Two quirks worth knowing before your first loop. Reasoning is mandatory on these models: settings like reasoning_effort: "none" come back as errors rather than being quietly ignored, so sloppy OpenAI drop-in code can fail loudly — better than silently, but plan for it. And reasoning tokens burn against your output cap, so set generous maximums; a tight cap buys you empty replies, as our census probes found out so yours don’t have to.

    What this does not prove — yet

    One 52-second task proves the route works and the model can finish a small job cleanly. It does not prove Wonder’s ceiling, anyone’s reliability across a month of autonomous loops, or behavior under production load — and this desk won’t claim otherwise. The head-to-head that would actually settle the seat question — Composer vs. Spark in Cursor vs. Wonder through this API, same work order, same scoring — is scheduled and unrun, and it’s named that way on the desk’s front page. When it runs, it lands here, numbers and all, whichever way it cuts.

    Prices, tiers, and the one discount that should make you read the fine print twice are on the desk’s pricing page: Meta Model API Pricing & Limits.