How to publish your first agent to the HUMΛN Marketplace
HUMΛN Team··12 min·Builders
Who this is for
You already built an agent or bundle. You want distribution without turning your work into unmanaged shadow IT in buyer orgs.
Review process (what reviewers look for)
- Provenance integrity — Clear actor boundaries; no hidden privilege expansion.
- Connector honesty — Scopes match README claims; secrets handling is least-privilege.
- Governance fit — Policy hooks exist where outputs leave the sandbox (email, money movement, customer-visible text).
- Mission alignment — No surveillance-by-stealth; no duplicative native harm.
Governance requirements you should expect
Publishing is not “upload zip.” Bundles ship with governance configuration so installs inherit controls — reviewers check that defaults are safe and documented.
What a strong listing includes
- One sentence outcome — Who saves time, what risk is reduced.
- Explicit boundaries — What the agent will not do without human gates.
- Evidence of testing — Screenshots of builder runs, artifact examples, escalation paths.
- Support posture — How buyers get updates; compatibility notes.
Listings that read like generic AI blurbs get ignored; listings that read like operational runbooks get installed.
Revenue and visibility
Model details evolve — treat Marketplace as distribution with accountability, not a passive app store. Enterprise traction follows trust artifacts (audit-friendly behavior) more than keyword stuffing.