Version 1 · last updated 2026-10-13
September 2026
Ask pages answer with three depths of citation
Every sentence carries a marker to the fact it came from; every source opens to say in words how it got onto the record. Refusals name the reason and what was searched. Starter and follow-up questions come only from what the record holds.
A new retrieval engine, judged by 125 cases
Follow-ups ("and where?", "which one?", "is that still true?") resolve against the thread. Typos in names are corrected and flagged. Injection text is stripped and flagged. Absence is reported as absence, never as a "no".
Owners can let a model phrase answers, per page, off by default
The model sees only the record, may only re-phrase facts retrieval already found, is validated against the record, and every such answer is labelled. Daily caps per page and per asker; an operator kill switch and fuse.
Owners see what each answer cited and correct at the fact
The Questions tab lists the facts behind every answer with "Confirm still true"; an owner answer can be unpublished without deletion.
The coverage boundary
An Ask page states what the record can answer. Owners may also publish how often people asked about things it cannot, as counts by category, never text.
Owner-written starter questions and refusal wording
Up to four starters, shown only when they resolve against the record. A note in the owner's words on a not-on-the-record refusal; the behaviour stays fixed.
Readers can flag a source
One tap under any citation says "this source does not support the answer"; it lands in the owner's inbox against the question.
Appeals have a public route
A suspended person appeals at /appeal without logging in; a human decides in the operator console.
A recovery-email change is its own proof step
The link goes to the new address and is the only path that ever changes an account's email.
Icons, manifests, and a home-screen page
A complete icon set from one mark; a per-person web manifest so a saved page is that person, not the product.
Public pages: what Moi does not do, comparisons, this changelog, a transparency report, and llms.txt
Each negative tied to its doctrine bar; each comparison concedes shared capability before differentiating; the report is computed live.
Operator console caught up
Ask Moi, errors and operators sections; model spend against caps; suggested blocks from what was refused.
Import from Linktree or hoo.be
Paste the address of your page and it is drafted from it: one fetch, at your request, everything editable before publishing. Facts that came this way say so in their provenance.
Six themes and two layouts
The look is yours to pick in the editor and change live from the dashboard; nothing about the record changes.
A tip jar as a link
Point at the tipping service you already use. Moi is not in the payment path, so the fee is 0 by construction.
Every page states its consent boundary and its freshness
"Read by AI systems only with X's consent" with the classes allowed and withdrawn, and "every fact here was confirmed within the last N days", on the page and in the record.
Every answer has an address
A permalink re-renders a cited answer from the current record, and says so if the record has changed since.
Your own domain, proven by DNS
Claim a domain, add one TXT record, and the page is served there as the canonical address; moi.me/name redirects. Certificates are issued by the host only for proven domains. A website can be proven the same way, free, without routing.
Clicks, human days, and asking about your numbers
Link clicks are counted by kind of reader without a script; the dashboard leads with distinct human visiting days, never raw hits; and a question box answers from the counts.
All months: /changelog.