Skip to content
GenCreatorDelivery room

The first ten minutes of a GenCreator product should create proof.

This is the self-serve delivery layer: starter packets, agent-readable manifest, fulfillment contracts, support boundaries, and the checkout blockers that must be wired before proposed products become paid products.

Generate kitDownload startersOpen manifest APICheckout mapProduct suite

Activation sequence

Artifact before access

10 min win
1

Read the OS contract

Use the Creator OS Contract to understand the full brand, product, agent, MCP, community, and Studio architecture before choosing a path.

2

Open the brand social system

Use the Brand Social System to lock logo, type, social formats, carousels, video frames, GTM assets, source credit, and approval rules before producing public media.

3

Generate the intelligence packet

Use the Creator Intelligence System to compose one source signal into the product decision, MCP plan, skill path, campaign handoff, community route, pricing, offers, and approval policy.

4

Package the offer system

Use the Product Offer System to turn the intelligence packet into offer ladder, delivery experience, launch assets, checkout truth, MCP plan, community bridge, and Studio boundary.

5

Generate a creation packet

Use Creation Engine to turn one source signal into drafts, proof checks, assistant roles, MCP plan, offer path, and community review.

6

Activate the operating path

Use Activation Engine to turn the packet into seven days of product, agent, approval, community, and Studio routing.

7

Generate the learning path

Use Learning Path Engine to choose the education, product, skill pack, MCP, community, pricing, offers, and Studio sequence from the creator state.

8

Run the readiness diagnostic

Score memory, signal, packaging, agent readiness, approval safety, and community practice before choosing a product or support layer.

9

Generate the proof loop

Turn one finished artifact into a review request, weekly proof loop, stage handoff, assistant prompt, and support boundary before joining community.

10

Open the Community OS

Compose the proof loop, Creator Vault state, product ladder, launch moves, MCP resources, and Studio boundary into one operating room.

11

Choose the artifact

Start with the packet that solves the immediate bottleneck: memory, campaign production, agent installation, or community review.

12

Generate the campaign packet

Use Campaign Studio when the bottleneck is distribution, proof, channel fit, or approval-safe content output.

13

Generate the kit

Use the composer to turn the artifact into modules, prompts, MCP resources, checkout handoff, and activation rhythm.

14

Install one skill

Choose a mode-safe skill pack so the assistant knows the workflow, lesson, MCP resources, and approval boundary.

15

Download or inspect

Use the markdown sample or the manifest API. The paid version later adds templates, examples, and delivery automation.

16

Create one usable output

The first sitting must produce a filled vault row, campaign brief, or assistant task with an approval rule.

17

Route into practice

Finished artifacts move into community review or Studio only when the self-serve system is already producing proof.

Downloadable starters

These are sample artifacts, not vague feature lists.

Each starter is intentionally small. The kit composer now combines these pieces into a buyer-ready packet before the paid versions add templates, examples, delivery automation, and update rights.

Build from the composer
sample10 min

Creator Vault Kit starter

Create the first memory layer: voice, offer, audience, proof, and approval policy.

  • Vault schema
  • Voice rules
  • Offer map
  • Proof table
  • Approval policy
Download markdown

creator-vault-kit-starter.md

live2 min

Creator Vault operating state API

Compose one creator artifact into vault memory, product handoff, MCP resources, approval backlog, and community review.

  • Vault memory
  • Product handoff
  • MCP resources
  • Approval backlog
  • Community review
  • First seven days
Open API

gencreator-creator-vault-state.json

sample10 min

Campaign Pack System starter

Turn one signal into a draft packet with risk checks and approval notes.

  • Signal intake
  • Campaign brief
  • Platform drafts
  • Reply bank
  • Approval checklist
Download markdown

campaign-pack-system-starter.md

live3 min

Campaign Studio API

Generate one draft-only campaign packet with proof checks, approval task, community bridge, and product handoff.

  • Draft assets
  • Proof checklist
  • Approval task
  • Postiz-style export
  • Assistant prompt
  • Product handoff
Open API

gencreator-campaign-studio.json

sample10 min

Agent and MCP Pack starter

Install the GenCreator assistant role and decide which tool mode is allowed.

  • Agent role
  • Tool modes
  • MCP endpoint
  • Approval tasks
  • Safety checklist
Download markdown

agent-mcp-pack-starter.md

live2 min

Agent-readable product manifest

Let an assistant inspect products, artifacts, statuses, and delivery paths.

  • Products
  • Artifacts
  • Tool surfaces
  • Support boundaries
  • Next build order
Open API

manifest.json

live2 min

Creation Engine API

Generate a creation packet from one signal with drafts, proof checks, agent plan, MCP plan, offer path, and community review.

  • Creation brief
  • Draft artifacts
  • Proof checks
  • Agent plan
  • MCP plan
  • Offer path
  • Community review
Open API

gencreator-creation-engine.json

live2 min

Activation Engine API

Generate a seven-day activation plan from a creation packet with product path, MCP plan, community handoff, and Studio escalation rules.

  • Seven-day plan
  • Product path
  • MCP plan
  • Community handoff
  • Education path
  • Escalation rules
Open API

gencreator-activation-plan.json

live3 min

Product Offer System API

Turn one creator signal into an offer ladder, delivery experience, launch assets, MCP plan, community bridge, and Studio boundary.

  • Offer ladder
  • Delivery experience
  • GTM moves
  • Launch assets
  • MCP plan
  • Community bridge
  • Support boundary
Open API

gencreator-product-offer-system.json

live2 min

Agent and MCP Pack manifest

Let an assistant inspect roles, install targets, MCP resources, and prompt contracts.

  • Agent roles
  • Install targets
  • MCP resources
  • Prompt contracts
  • Community handoff
Open API

agent-pack.json

live2 min

Agent Pack install bundle

Inspect role files, MCP config, Eve operating role, approval policy, and install checklist.

  • Role files
  • MCP config
  • Eve role
  • Approval policy
  • Install checklist
Open API

agent-pack-bundle.json

live2 min

Eve Command Center API

Generate product route, proof questions, role stack, skill install plan, MCP policy, approval queue, campaign handoff, and community loop for one artifact.

  • Proof questions
  • Role stack
  • Skill install plan
  • MCP policy
  • Approval queue
  • Campaign handoff
  • Community loop
Open API

eve-operating-brief.json

live2 min

Creation Workspace session API

Compose one artifact into Blueprint, Eve, checkout handoff, MCP resources, and community review.

  • Artifact state
  • Blueprint
  • Eve brief
  • Checkout handoff
  • Community review
Open API

creation-workspace-session.json

live2 min

Self-Serve Kit API

Generate a buyer-ready operating packet from workspace state, focus, and delivery style.

  • Product modules
  • Assistant prompt
  • MCP resources
  • Checkout handoff
  • Activation plan
Open API

gencreator-self-serve-kit.json

live2 min

Skill Pack Library API

Inspect installable creator skill packs, lessons, prompts, MCP resources, modes, and support boundaries.

  • Skill files
  • Prompts
  • MCP resources
  • Lessons
  • Community practice
Open API

gencreator-skill-pack-library.json

live2 min

Creator OS API

Inspect the full GenCreator brand, product, service, MCP, community, Eve, and roadmap architecture.

  • Mission
  • Brand assets
  • Product layers
  • Diagnostics
  • Offers
  • MCP resources
  • Eve boundary
  • Roadmap
Open API

gencreator-creator-os.json

live2 min

Brand Social System API

Inspect the logo, typography, platform format, carousel, video, GTM, and assistant prompt contract before producing public brand assets.

  • Logo rules
  • Type rules
  • Social formats
  • Carousel systems
  • Motion systems
  • GTM plays
  • Assistant prompts
Open API

gencreator-brand-social-system.json

live2 min

Creator Intelligence System API

Compose one creator signal into a product decision, composed engines, MCP plan, skill path, community route, offers, pricing, and approval policy.

  • Product decision
  • Composed engines
  • Operating graph
  • MCP plan
  • Skill packs
  • Business model
  • Approval policy
Open API

gencreator-creator-intelligence-system.json

live2 min

Creator Readiness Diagnostic API

Score the creator operating system and choose the next product, assistant role, MCP resource, community step, or Studio gate.

  • Operating score
  • Readiness dimensions
  • Priority layer
  • Product path
  • MCP resources
  • Eve prompt
  • Community handoff
Open API

gencreator-creator-readiness-diagnostic.json

live2 min

Learning Path API

Generate a self-serve learning path with modules, skill packs, MCP resources, product handoff, community bridge, and Studio boundary.

  • Learning modules
  • Skill path
  • MCP plan
  • Product handoff
  • Community bridge
  • 1:1 boundary
Open API

gencreator-learning-path.json

live5 min

GenCreator.community onboarding

Enter the community with one artifact, one question, and one weekly proof loop.

  • Artifact intake
  • Proof loop
  • Review request
  • Agent habit
  • Upgrade path
Open route

community-onboarding

live2 min

Community Proof Loop API

Generate the review request, weekly proof loop, product path, assistant prompt, and support boundary from one artifact.

  • Review request
  • Weekly proof loop
  • Community post draft
  • Stage handoff
  • MCP plan
  • Support boundary
Open API

gencreator-community-proof-loop.json

live2 min

Community OS API

Compose one artifact into the GenCreator.community operating room with vault state, proof loop, offer bridge, launch moves, MCP plan, and Studio boundary.

  • Operating rooms
  • Readiness score
  • Weekly loop
  • Product ladder
  • GTM moves
  • MCP plan
  • Support boundary
Open API

gencreator-community-os.json

Product readiness

Proposed products become paid products only when delivery is honest.

The public page can now show sample value. The next engineering step is payment-linked fulfillment: checkout success, email delivery, product analytics, and Whop product ID mapping.

plannedParked

Studio

Get a review path for the offer, campaign, and agent workflow already in motion.

studio_interest_redirected_to_creator_mission

Delivery path is application-led.

Waitlist or inspectOpen checkout contract

Fulfillment contracts

Each paid offer has a buyer promise and a support boundary.

This is the delivery standard before checkout goes live: entitlement key, gated assets, email subject, update cadence, and the next practice layer.

creator_vault_kit

Creator Vault Kit

Create the voice, offer, audience, proof, and approval memory layer before any assistant drafts.

Gated assets

  • Full Notion-ready vault tables
  • Voice rule examples
  • Offer map examples

Self-serve setup, product updates, and community review path. No private implementation support.

Join waitlist

campaign_pack_system

Campaign Pack System

Turn one signal into a campaign brief, platform drafts, reply bank, and approval checklist.

Gated assets

  • Campaign templates
  • Example campaign packets
  • Hook decoder prompts

Self-serve templates and examples. Campaign judgment happens in community or Studio.

Join waitlist

agent_mcp_pack

Agent and MCP Pack

Install GenCreator roles, MCP resource contracts, prompt contracts, and approval-first operating modes.

Gated assets

  • Full role files
  • MCP config examples
  • Install bundle manifest

Install instructions and updates. Custom agent implementation belongs in Studio.

Join waitlist

gencreator_community

GenCreator.community

Enter with one artifact, one review question, one Community OS packet, and one weekly proof loop.

Gated assets

  • Member Community OS template
  • Member proof loop template
  • Review request format

Community practice, examples, and review rituals. Studio is the direct review layer.

Join waitlist

Transactional handoff

Every paid product now has a fulfillment email contract.

Whop can map a payment event to one internal product, send the exact buyer email, record the event, and expose the same contract to assistants through the fulfillment API.

creator_vault_kit

Your Creator Vault Kit is open

Creator Vault Kit is open. Start with one artifact, then route the result into practice.

first link

/downloads/gencreator/creator-vault-kit-starter.md

Open fulfillment APIPreview success route

campaign_pack_system

Your Campaign Pack System is open

Campaign Pack System is open. Start with one artifact, then route the result into practice.

first link

/downloads/gencreator/campaign-pack-system-starter.md

Open fulfillment APIPreview success route

agent_mcp_pack

Your Agent and MCP Pack is open

Agent and MCP Pack is open. Start with one artifact, then route the result into practice.

first link

/downloads/gencreator/agent-mcp-pack-starter.md

Open fulfillment APIPreview success route

gencreator_community

Welcome to GenCreator.community

GenCreator.community is open. Start with one artifact, then route the result into practice.

first link

/community/onboarding

Open fulfillment APIPreview success route

Checkout readiness

The sales system needs fulfillment proof before stronger claims.

This keeps the offer premium and clean: buyers know what exists, what is proposed, what happens after checkout, and where community or Studio begins.

Inspect checkout readiness
Gate 1The buy resolver now gives every paid product one internal checkout handoff.
Gate 2If a Whop checkout URL is present, the resolver redirects there. If not, it falls back to the readiness contract.
Gate 3Checkout success routes and fulfillment email previews exist as buyer delivery targets.
Gate 4Whop product IDs, checkout URLs, success redirects, and paid bundles should map to this manifest before public paid launch.
Gate 5Support boundaries stay explicit: self-serve includes instructions and updates, not unlimited private help.