Who builds Ansengine, and what it will not claim

Ansengine measures whether an AI answer names your brand, whether it cites your pages, and whether what it says about you is supported by a source. Three rates, one question at a time, one engine at a time.

Every rate carries the number of runs behind it and the range it could honestly be. A rate built on four answers prints as a rate built on four answers, because the count is the difference between a finding and a feeling.

There is no rank position anywhere in the product. Position in an AI answer is not stable across repeated runs, so a rank is a number that looks precise and means nothing. We would rather sell a smaller true number.

Every question is asked more than once, because the answer changes between runs. A single run is an anecdote, and a product built on anecdotes cannot tell you whether anything you did worked.

Every engine is measured on its own and reported on its own. Engines agree on only a small share of the sources they cite, so an average across them describes no surface a buyer ever opens.

Movement is reported only when the ranges stop overlapping. A difference that could be noise is labelled normal variation, on every plan, at every price. Anything unmeasured renders as a dash and never as a zero.

Every plan includes 3 engines and can add 6 more per question. The included set is the consumer apps buyers actually open, not the cheapest endpoints to poll.

ChatGPT is read on chatgpt.com, the app your buyers use, rather than only through the developer API. The two do not return the same answers, and reporting the API alone would flatter every number on this site.

Developer APIs are measured and reported on their own line, never averaged into a headline with the consumer apps.

The free report is a real baseline and not a teaser: 10 buyer questions, asked 5 times each, across 4 answer surfaces. That is 200 measured answers, every one stored with its sources, and no card.

On a plan the measurement continues on a cadence, the fix queue is ranked by what it would move, drafts are written from facts you verified, and nothing reaches your own site until you approve it.

Receipts confirm a win only when the ranges separate. Every answer downloads as CSV and every payload as JSON, so any number we print can be checked outside this product.

Schema markup and llms.txt are hygiene. They are not ranking levers for AI answers, and we say so on the page where a competitor would be selling them to you.

No rank positions. No invented statistics. No star ratings, review counts or aggregate ratings on our own pages, which is the shortcut this category takes by default.

No public or irreversible action without a human approval. The agent drafts, you approve, the system acts.

Our own grades are published on the methodology page: a hand labelled golden set for each stage of the pipeline, the score it reached, the bar it has to clear, and the date it last ran. A stage that did not run says so rather than showing a zero.

The enforcement page names the test that fails if we break one of the rules above, so a claim on this site is backed by something that can go red.

Every page on this site carries the commit that served it, in a meta tag named ansengine-build. Any claim here can be checked against the exact code that made it.