Skip to content

Become a Kreator

The Kreator programme, stated plainly: what is live today, what is partly built, and what is not open yet

This page carries the reviewed programme status — the same single source the Kai assistant answers from in the Creator Hub. If something is not listed as live, it is not open yet, and no dates are promised.

Kreator programme — what is live today

Start here

This page is the single source for what the Kreator programme does and does not do right now. If something is not listed as live, it is not open yet, and no dates are promised.

Statuses: live (you may rely on it today) · pilot (partly built, expect gaps) · planned (being built, no dates) · unverified (not confirmed end to end — treat as not available).

  • [live] You can apply to become a Kreator; access is reviewed and approved by the Kaoohi team — Today via account settings; the public apply form is plan K1.2
  • [live] Each Kreator has a public profile page
  • [live] Actors are published from a container image and pass a security scan
  • [live] A human reviews every actor, and it needs at least one use case
  • [live] Free actors from outside Kreators can be listed in the store
  • [planned] Selected Kreators get the actor template and a guided first build
  • [pilot] A sandbox lets you try your actor before submitting
  • [pilot] You see usage and ratings for your actors
  • [live] Actors built on the template can switch between OpenAI and Anthropic models — Say "the template supports", not "any model"
  • [planned] Kreators can sell paid actors
  • [planned] Kreators are paid a share of the reference price — Never quote a percentage
  • [planned] Kreators choose a price from a reference grid
  • [planned] Kaoohi acts as the seller and as AI Act provider, so the Kreator is the author, not the seller — Not legal advice in chat
  • [unverified] You can describe an actor in plain language and have it generated (Actor Studio)
  • [unverified] A sole proprietor can be a Kreator
  • [live] An AI community manager helps you in the Creator Hub, with people behind it for contract and payment questions — Kai panel on every Creator Hub page; /home/tools/kreator-support routes handoffs to people

Never listed because they are false today: n8n / Make / Zapier import, bring-your-own-keys for Kreators, Free / Pro / Enterprise plans, paid listings and payouts (payouts are planned — figures are not final and no share percentage may be quoted).

Publish your actor

What publishing involves

  • Prepare a container image of your actor with an explicit tag — latest and stable are rejected. Example: ghcr.io/your-org/your-actor:v1.0.0.
  • If the image lives in a private registry, provide pull credentials in the publish wizard; they are used to pull the config and are stored in Vault, not in the actor row.
  • In the Creator Hub, open the publish wizard and register the actor from the image. You can override the name, description, category, tags and pricing model the image declares.
  • Add at least one concrete use case — an actor with no use case cannot be approved.
  • Optionally add submission notes for the reviewer (what changed, what to look at).
  • Submit for review. The actor moves to pending_review, a security scan runs against the image, and a human reviewer makes the decision.

Review states

  • draft — not submitted yet; only you can see it.
  • pending_review — in the queue; the security scan runs here.
  • revision_requested — the reviewer sent it back with notes. Fix the notes, rebuild the image with a new tag, and resubmit.
  • rejected — the stated reason explains why; some issues can be fixed and resubmitted.
  • approved — listed in the store; usage and ratings appear on your actor page.

Changing a published actor

Updating the image tag re-runs extraction. Breaking config changes (removed tools, changed config fields) put the actor back into review automatically. Non-breaking changes update in place.

Pricing

Free listings are open. Paid listings and payouts are not open yet — see the programme status page. Do not set prices expecting them to be chargeable today.

The security scan

Every actor goes through an automated security scan of its container image before a human reviews it. The scan runs when the actor enters review and again whenever the image tag changes.

What you will see

Each scan run has a status — queued, running, done, or error — and, when done, a recommendation with findings and reasons. Your dashboard and this assistant show the latest scan for the actor's current image; findings from older images are stale by definition.

Common findings and the legitimate fixes

  • A credential or secret inside the image — an API key, token or password. Remove it from the image and the repository, pass it at deploy time as a secret parameter instead, rebuild with a new tag, and resubmit. The scan finding clears because the secret is gone — not because it is hidden.
  • Outbound calls the config did not declare. If your actor calls an external host, declare that egress in its config so the platform knows what to expect, then rebuild and resubmit.

What this assistant will not do

Explain how the scanner detects things or how to avoid detection. There is no legitimate version of that question — the fix is always to make the image match what the config declares.

If a scan looks stuck

Scans can queue behind others. If the same run stays in a non-final state for a long time, ask for a person here in the hub and the team will look at it.

What the reviewer checks

A human reviews every actor before it is listed. There is no auto-approval and no self-serve listing — that is deliberate: a curated catalogue is slower and worth it.

What the reviewer checks

  • The security scan result for the current image (see the security scan page).
  • At least one concrete use case attached to the actor. "It is a general assistant" is sent back.
  • That the listing describes what the actor actually does — name, description, category and tags that a buyer could rely on.

Why actors get sent back

The most common reasons: no use case attached, a scan finding that needs a fix (see the security scan page for findings and their legitimate fixes), or a description that does not match the config. A send-back is revision_requested, not a rejection: read the feedback sent back, fix it, rebuild the image with a new tag, and resubmit.

How long does a review take?

A review is done by a person, so there is no fixed turnaround and none is promised. If yours has been waiting a long time, ask here in the hub and the team will check.

Kreator quickstart — from zero to a listed actor

The short version: get the template, build your actor as a container image, register it in the publish wizard, submit for scan and review, get listed. Each step says where it happens and what done looks like; the detail pages carry the rules.

A first clean build was measured on 2026-10-05 (5-CPU laptop, cold Docker engine): 9 seconds to generate the actor from the template, just under 2 minutes to build the image, 6 seconds to push it — about 2 and a quarter minutes of machine time from nothing to a pushed image. Registration, scan and review are human-paced and not counted.

0. Before you start

  • Kreator access approved on your account (request it from your account settings; a person reviews it).
  • Docker or an equivalent way to build a container image.
  • A registry you can push to. Private-registry credentials can be added at registration.

1. Get the actor template

Actors are generated from the actor template (kaboum), which founding-cohort Kreators get private access to. It supports both OpenAI and Anthropic models — you switch by configuration, not by rewriting code. What you owe it: your actor logic, its config schema, and honest metadata.

2. Build the image

Build and push a container image you control. The image rules (explicit tags, no baked-in secrets) are on the publishing page — read them before your first build.

3. Register in the publish wizard

In the Creator Hub, open the publish wizard and register from the image; it pulls your config for review. You can override the declared name, description, category and tags. Want a second pair of eyes first? Paste the config JSON into the chat panel and it gets checked against the same schema the wizard uses.

4. Submit

Submitting queues the security scan and a human review. The publishing page explains the review states and what a send-back means; the scan page explains findings and their legitimate fixes.

5. Listed

Once approved, the actor is listed in the store and appears on your public profile page. Free listings are open today; paid listings are not — the programme status page says exactly what is live.

When something goes wrong

Ask in the Creator Hub chat: it can check your config, explain scan findings and review feedback, and hand you to a person for anything about contracts, payouts or disputes. The quickstart gets better from what Kreators ask.