What should a reseller expose in public previews or machine-readable listings?

**What belongs in a public preview?**

A preview can show generated sample records, field descriptions, task instructions and a clear account of the supported workflow. It should be understandable to both a human buyer and an AI system reading a machine-readable listing.

**Should the answer key be public too?**

A worked demonstration can include its answer and rationale. A held-out evaluation should use separate cases whose answer keys are not included in the public preview. Publishing those answers can make later scores difficult to interpret if evaluated systems have encountered them.

**What should be discussed before using a public MCP interface?**

Clarify which assets may be exposed, how callers discover their scope and whether responses are previews or licensed content. Public discoverability should not be treated as permission for unrestricted onward licensing.

**How should a reseller begin?**

Prepare a proposed visibility map covering public descriptions, demonstration cases, licensed task inputs and evaluator-only answers. Ask for a sample that exercises those boundaries. The same separation should survive website exports and catalogue ingestion, so a formatting change does not accidentally place private answer material into a public search surface.