A generator that scores its own output is worth little. A public provenance endpoint returning the source URL, the quality-gate scores, per-skill byte counts and a bundle sha256 is worth a great deal, because somebody other than the seller can run it. That matters most on the marketplace side, where you are weighing a package you did not produce. Two things to consider before selling here: the persona feature creates a public seller identity that reads as independent while your ownership stays private, and the platform's cut and payout routing are stated in the tools themselves. agent_delete refusing while a persona still has sold or claimed skills is the right refusal — buyers keep their access.
A skill-generation server with a marketplace attached: extraction from a content source, a public provenance check on the result, a catalogue, and listing, purchasing and seller-persona management.
- generate_skills, analysing a YouTube video, article, PDF or image URL and returning ranked skill packages — each with a SKILL.md covering principles, failure modes and implementation steps, a README, reference files and a test script, ready to save into a skills directory
- estimate_cost, giving the token and dollar cost of a generation before it runs — described in its own text as heuristic at v1
- get_quota, the calls used, the monthly limit and the plan name for the key in the environment
- verify_artifacts, the provenance manifest for a past generation: source URL, theme plan, quality-gate scores, per-skill artifact byte counts and the bundle sha256 — a public endpoint that also reports which billing path produced it
- The catalogue: list_skills as a compact scannable summary, and get_skill for one record's full artifacts, MCP, safety, governance, references and FAQ
- Marketplace browsing without a key or a purchase: search by query, category, free-or-paid and sort order, and one listing's detail — with the package contents locked until you own it
- marketplace_purchase, granting free skills immediately and returning both a Stripe Checkout URL and an x402 USDC payment challenge for paid ones
- Selling: a package published from files or markdown at a chosen price, your listings and your library, and seller metrics covering sales, downloads, gross and net earnings, platform fee and payout status
- AI seller personas created, listed with per-persona metrics and masked payout wallet, updated, and deleted — with deletion refused while the persona still has sold or freely-claimed skills
A Loreto API key in LORETO_API_KEY for generation, quota, your own listings and library, seller metrics and the persona tools. Two work without one: verify_artifacts is a public endpoint, and marketplace browsing needs neither a key nor a purchase. Paid purchases settle through Stripe, or through x402 in USDC for wallet-holding agents.
One command plus a key — uvx loreto-mcp, then supply credentials