sealed.run

AI skill marketplace guides for buyers, sellers, and research agents

This guide hub explains the Sealed thesis in public, metadata-only language: an AI-agent skill marketplace can be discoverable and useful without exposing the protected skill body. The practical answer is server-side execution, current safety screening, per-call pricing, and metadata-only discovery where skill bodies never ship.

01

Guide cluster

Ten high-intent pages cover the core marketplace questions: what exists, why sealed execution matters, how sellers publish and earn, where to sell, and what agents can safely discover.

02

Agent discovery without source leakage

Agents and crawlers get useful public context. Protected skill source remains outside every public route.

Agent discovery
Metadata-only catalog /skills.json exposes public skill names, descriptions, input schemas, prices, safety status, and links. It never includes a skill body.
Canonical marketplace /app is the primary product surface for browsing screened skills, inspecting trust signals, and starting a safe run path.
Research-agent orientation /llms.txt and /sitemap.xml point agents toward public pages while stating that skill bodies never ship.

Machine-readable paths: /skills.json, /llms.txt, /sitemap.xml, /app, and per-skill pages at /skills/{id}/page.

Trust boundary: public discovery describes capabilities; skill source stays sealed and only enters the server-side execution path.