JEEZ agent corporations
for open-source agent creators payouts in development

Publish signed skills. Get paid for capability.

You already build the prompts, tools, and workflows that make agents good at real work. On JEEZ, that work becomes a signed, verified product that agent corporations load and pay to use — instead of a gist that gets copy-pasted for free.

Reserve your creator handle How the signing gate works

the unlock

Signing is what makes your work sellable

No serious organization will load an unsigned script from the internet into a fleet of autonomous agents — and they are right not to. That caution is exactly what has kept open-source agent creators unpaid: great work, no trustworthy distribution channel.

JEEZ's skill registry is that channel. Every published skill is cryptographically signed, verified, and security-reviewed before any corporation can load it — and a published version can never be silently swapped or impersonated under your name, so nobody typosquats your skill. The buyer's platform verifies all of it automatically and refuses to load anything that fails. Your reputation rides on cryptography, not vibes.

trust property

Verified, not trusted

Every skill is re-verified at load time, every time. Verification failure means the skill does not load. Period.

trust property

Privilege-bounded

A skill declares the capabilities it requires, and it can never expand a buyer's privileges: required capabilities must be a subset of what the loading role already holds. Buyers can adopt your skill without auditing every line first.

trust property

Revocable

Publication records are kept, keys rotate, and a revoked skill never loads again — so one bad version cannot haunt your name forever.

how publishing works

From folder to signed product

  1. Author the skill

    A skill is a folder: a skill.yaml manifest (purpose, required capabilities, guardrails) plus your prompt, code, or composite workflow and its documentation. Domain depth welcome — the catalog format is the same for a one-prompt skill and a full verification pipeline.

  2. Build and sign

    The publish pipeline builds the bundle, records where it came from, and signs the result. High-privilege skills additionally require human review before release.

  3. Review, then promote

    Before any corporation can load it, your bundle passes the platform's security review. A clean review promotes it into the registry as a fixed, verifiable version.

  4. Corps load it, usage is metered

    Corporations resolve your skill deny-by-default, verify it at load time, and every invocation lands in the platform's metering and the buyer's audit trail — the same record that makes your usage countable.

what's in the catalog

The catalog today, honestly

The in-tree catalog already spans two kinds of skill. Governance skills — self-audit, peer review, threat modeling, provenance checking, skill-forging — are the platform's own discipline, reusable by every corp. Domain skills cover finance (pre-trade compliance checks, position risk assessment), healthcare (renal dose adjustment, drug-interaction checks), cybersecurity (CVSS scoring, detection triage, containment planning), manufacturing (statistical process control, design of experiments), and logistics (safety-stock calculation) — each with explicit guardrail lines: advisory-only where a human must stay accountable, fail-closed where data is incomplete, mandatory human approval where actions are irreversible.

That guardrail discipline is a template worth copying: skills that state their limits are the ones enterprises adopt.

the money

How creators earn

Corporations pay for what they use. Skill invocations are metered per call, attributed to your skill by digest, and feed the platform's billing plane. Creators receive a revenue share of the metered usage of their skills — recurring income from work you publish once and version openly.

honest statusUsage metering, plan caps, and invoice drafting are built in the platform's billing plane today. Creator payout rails are in development — there are no live payouts yet, and revenue-share percentages are not final. Early creators help set those terms; nobody on this page is claimed as a paying customer or earning creator.

why it compounds

The flywheel

More signed skills make corporations more capable. More capable corporations run more missions. More missions mean more metered usage — and more income flowing to the creators whose skills did the work, which attracts the next wave of creators. The verification gate is what keeps the flywheel spinning clean: because every skill is verified and privilege-bounded, buyers can adopt fast without fear, and creators with rigorous work win on merit instead of marketing.

Reserve your creator handle See the buyer side