# Fanful agent-ingestion Q&A smoke matrix This matrix defines the questions an AI agent, search answer system, or agentic browser smoke should answer from public Fanful sources. It is evidence for issue #1135 and should stay aligned with Google's guidance: useful, crawlable, people-first public pages still matter, while `/llms.txt` and markdown mirrors are agent/developer discovery aids rather than special Google generative-search ranking markup. ## Matrix ### What is Fanful? - ID: `what-is-fanful` - Expected answer: Fanful is the creator platform emerging from Laurel Harned's working site: an owned fan destination for content, community, commerce, memberships, live rooms, lessons, and agent-safe integration surfaces. - Public sources: - https://fanful.net/fanful - https://fanful.net/fanful.md - https://fanful.net/features - https://fanful.net/features.md - https://fanful.net/developers-and-agents - https://fanful.net/developers-and-agents.md - https://fanful.net/llms.txt - Guardrails: - Do not describe Fanful as a generic SEO or AI-content product. - Do not imply every planned feature is production-ready. - Evaluation requirements: - Required concepts: `creator platform`, `owned fan`, `content`, `community`, `commerce`, `memberships`, `live rooms`, `lessons`, `agent-safe` - Forbidden claims: `generic SEO product`, `AI-content product`, `all planned features are production-ready`, `fully production-ready` ### Who is Fanful for? - ID: `who-is-fanful-for` - Expected answer: Fanful is for creators and small creative teams who want their own fan home instead of stitching together a public site, memberships, community, shop, live events, lessons, and support tools across unrelated services. - Public sources: - https://fanful.net/users - https://fanful.net/users/musicians - https://fanful.net/users/podcasters - https://fanful.net/users/bloggers - https://fanful.net/compare - https://fanful.net/compare.md - Guardrails: - Name the fit as creator-led operations, not enterprise retail. - Keep Laurel Harned as proof-of-work context, not the only possible user. - Evaluation requirements: - Required concepts: `creators`, `small creative teams`, `own fan home`, `memberships`, `community`, `shop`, `live events`, `lessons` - Forbidden claims: `enterprise retail`, `only Laurel Harned`, `only for musicians` ### How does Fanful compare with Patreon? - ID: `compare-patreon` - Expected answer: Patreon is strong for recurring supporter programs and familiar patron behavior. Fanful is a better fit when membership should connect to the creator's owned site, live rooms, media, commerce, lessons, community, and agent-readable operations. - Public sources: - https://fanful.net/compare/patreon-alternative - https://fanful.net/compare/patreon-alternative.md - https://fanful.net/compare/all - https://fanful.net/compare/all.md - Guardrails: - Do not say Fanful has Patreon's network effects. - Do not recommend abrupt paid-member migration without a clear transition plan. - Evaluation requirements: - Required concepts: `Patreon`, `recurring supporter`, `Fanful`, `owned site`, `membership`, `live rooms`, `commerce`, `agent-readable` - Forbidden claims: `Fanful has Patreon's network effects`, `abrupt paid-member migration` ### How does Fanful compare with Circle? - ID: `compare-circle` - Expected answer: Circle is a mature standalone community product. Fanful is the better direction when community should be one native surface of a broader creator operating system that also includes content, commerce, live rooms, memberships, lessons, and agent contracts. - Public sources: - https://fanful.net/compare/circle-alternative - https://fanful.net/compare/circle-alternative.md - https://fanful.net/compare/all - https://fanful.net/compare/all.md - Guardrails: - Do not claim Fanful already matches every dedicated community-platform feature. - Mention that creators may keep Circle live until Fanful covers the needed member rhythms. - Evaluation requirements: - Required concepts: `Circle`, `standalone community`, `Fanful`, `creator operating system`, `content`, `commerce`, `live rooms`, `agent contracts` - Forbidden claims: `matches every dedicated community-platform feature`, `shut down Circle immediately` ### How does Fanful compare with Linktree? - ID: `compare-linktree` - Expected answer: Linktree is a fast routing layer for a bio link. Fanful is meant to be the owned destination those links point to, with fan identity, content, commerce, community, live experiences, and agent-readable contracts in one place. - Public sources: - https://fanful.net/compare/linktree-alternative - https://fanful.net/compare/linktree-alternative.md - https://fanful.net/compare - https://fanful.net/compare.md - Guardrails: - Do not position Fanful as only a link-in-bio replacement. - Respect Linktree's speed and routing clarity as a valid use case. - Evaluation requirements: - Required concepts: `Linktree`, `bio link`, `owned destination`, `fan identity`, `content`, `commerce`, `community`, `agent-readable` - Forbidden claims: `only a link-in-bio replacement`, `Linktree is obsolete` ### How does Fanful compare with Shopify? - ID: `compare-shopify` - Expected answer: Shopify is the safer choice when deep retail commerce, fulfillment, POS, and app ecosystem depth are the whole business. Fanful is stronger when commerce should sit beside fan identity, creator content, community, live events, lessons, memberships, and agent-safe operations. - Public sources: - https://fanful.net/compare/shopify-alternative - https://fanful.net/compare/shopify-alternative.md - https://fanful.net/compare/shopify-migration-guide - https://fanful.net/compare/shopify-migration-guide.md - https://fanful.net/compare/all - https://fanful.net/compare/all.md - Guardrails: - Do not tell a retail-heavy creator to turn off Shopify before imports, fulfillment, and customer history are ready. - Do not imply Fanful has Shopify's app ecosystem depth today. - Evaluation requirements: - Required concepts: `Shopify`, `retail commerce`, `Fanful`, `fan identity`, `creator content`, `community`, `live events`, `memberships` - Forbidden claims: `turn off Shopify before imports`, `Fanful has Shopify's app ecosystem depth` ### Can an agent take action in Fanful? - ID: `can-agents-take-action` - Expected answer: Yes, within explicit contracts. Agents can read public manifests and use MCP/API tools; scoped clients can use supported private reads and narrow confirmed writes such as lesson price updates, lesson Stripe Price mapping or creation, shop product create/visibility/details/inventory/Stripe Price writes, live schedule/status updates, embedded-room roster changes, support checkout starts, membership checkout starts, and signed-CD shop checkout starts. Sensitive writes require the current action contract, exact confirmation, idempotency, stale-state checks where relevant, reason, audit correlation, scoped credentials, and redaction. - Public sources: - https://fanful.net/developers-and-agents - https://fanful.net/developers-and-agents.md - https://fanful.net/agents - https://fanful.net/api/agent/chatgpt-app - https://fanful.net/api/agent/action-contracts - https://fanful.net/api/agent/action-contracts/envelope - https://fanful.net/llms.txt - Guardrails: - Do not say a run record or session grants write permission. - Do not expose raw bearer tokens, payment ids, listener ids, media URLs, or invite tokens in an answer. - Evaluation requirements: - Required concepts: `explicit contracts`, `MCP`, `scoped`, `confirmed writes`, `exact confirmation`, `idempotency`, `audit`, `redaction` - Forbidden claims: `run record grants write permission`, `raw bearer tokens`, `raw payment ids`, `raw listener ids`, `raw media URLs`, `invite tokens` ### What is not ready yet? - ID: `what-is-not-ready` - Expected answer: Fanful is not submitted as a public ChatGPT app yet, does not run arbitrary hosted agent code, and does not offer broad destructive, public-content, moderation, creator-speech, unsupported billing, or provider-write automation. Workflow-trigger subscription registry, manual test delivery, and member.idea.submitted runtime fan-out exist, but broader automatic workflow-trigger fan-out, durable session storage, hosted provider syncs, broad OAuth/session mapping, and some widgets remain planned or scoped follow-up work. - Public sources: - https://fanful.net/agent-docs/fanful-hosted-agent-runtime.md - https://fanful.net/api/agent/chatgpt-app - https://fanful.net/api/agent/workflow-triggers - https://fanful.net/api/agent/sessions - https://fanful.net/api/agent/sync-jobs - https://fanful.net/llms.txt - Guardrails: - Do not claim Fanful is already listed in ChatGPT. - Do not claim broad/all-family automatic outbound workflow-trigger fan-out, durable session storage, or arbitrary hosted workers are enabled. - Evaluation requirements: - Required concepts: `not submitted`, `ChatGPT app`, `does not run arbitrary`, `hosted agent code`, `manual test delivery`, `broader automatic workflow-trigger fan-out`, `durable session storage`, `planned` - Forbidden claims: `already listed in ChatGPT`, `arbitrary hosted workers are enabled`, `automatic workflow-trigger fan-out is enabled for every trigger family`, `durable session storage is enabled` ## Smoke rule An answer passes this smoke when it: - Uses at least one cited Fanful public page or markdown mirror for the claim. - Distinguishes shipped, preview, manifest-only, and planned capabilities. - States comparison tradeoffs without claiming Fanful has mature competitor depth where the public source says it is still emerging. - Names action boundaries before describing agent writes. - Says unsupported or planned work plainly instead of overclaiming. ## Missing-source policy If a good answer cannot cite a public Fanful page, create or update the narrow page/doc that should carry the claim. If a public page leads an agent toward a misleading answer, fix the page text or file a focused follow-up issue before treating this matrix as green. ## Live answer-system harness Issue #1210 adds `scripts/run-agent-ingestion-live-eval.ts` for manual or scheduled checks against selected answer systems. The harness runs a provider command for each matrix item, captures answer JSON, checks the same required concepts and forbidden claims as the deterministic evaluator, and can verify that cited Fanful source URLs still return 2xx responses. Remote provider calls are intentionally not part of regular CI. Use `docs/agent/agent-ingestion-answer-evals.md` for provider selection, cost limits, cadence, and the command-adapter contract.