How to Submit to the Mentiko Marketplace

The Mentiko Marketplace is a community-driven registry where you can browse, install, and share automation workflows. Think of it as a package manager for agent chains -- instead of building every pipeline from scratch, you can grab a battle-tested chain someone else already built, install it, and customize it for your use case.

What's in the marketplace

The marketplace hosts four types of entities:

• Templates -- starting points for common workflows. A template gives you the skeleton of a chain with placeholder prompts and variable slots you fill in. Good for onboarding or standardizing patterns across a team.
• Chains -- complete multi-agent pipelines ready to run. A chain includes all agent definitions, event wiring, and variable declarations. Install it, set your variables, and execute.
• Agents -- standalone agent definitions you can drop into your own chains. A single-purpose agent with a well-tested prompt, like a code reviewer or a content editor.
• Artifacts -- reusable outputs from chain runs. Prompt libraries, research databases, or curated datasets that other chains can reference.

Anyone with a Mentiko instance can submit to the marketplace. Here's how.

Submission requirements

Before you submit, make sure your package meets these baseline requirements:

1. Valid chain.json with proper schema. Your chain definition must parse without errors and follow the Mentiko chain specification.
2. Complete agent definitions. Every agent in your chain must have all four required fields: name, prompt, triggers, and emits.
3. Description. One to three sentences explaining what your chain does and when you'd use it.
4. Category tag. One of: content, engineering, research, operations, sales, or support.
5. Difficulty level. One of: beginner, intermediate, or advanced. Be honest -- a chain that requires configuring three external APIs is not beginner-level.
6. Tested and working. Your chain must have run successfully at least once. We'll ask for a screenshot or log output from a successful run in your PR.

Chain JSON format

Your chain.json must follow this schema. Here's a complete example for a content pipeline:

{
  "name": "seo-blog-pipeline",
  "version": "1.0.0",
  "description": "Researches a keyword, writes an SEO-optimized blog post, and generates meta tags.",
  "category": "content",
  "difficulty": "intermediate",
  "variables": ["KEYWORD", "TARGET_AUDIENCE", "WORD_COUNT"],
  "agents": [
    {
      "name": "keyword-researcher",
      "prompt": "Research the keyword {KEYWORD} for {TARGET_AUDIENCE}. Identify search intent, related terms, and competing content. Save your analysis.",
      "triggers": ["chain:start"],
      "emits": ["research:complete"]
    },
    {
      "name": "blog-writer",
      "prompt": "Using the keyword research, write a {WORD_COUNT}-word blog post targeting {TARGET_AUDIENCE}. Optimize for the primary keyword {KEYWORD} with natural placement.",
      "triggers": ["research:complete"],
      "emits": ["draft:complete"]
    },
    {
      "name": "meta-generator",
      "prompt": "Generate an SEO title tag (under 60 characters), meta description (under 155 characters), and Open Graph tags for the blog post.",
      "triggers": ["draft:complete"],
      "emits": ["chain:complete"]
    }
  ]
}

The top-level fields version, description, category, difficulty, and variables are required for marketplace submissions but optional for local chains. The variables array declares every {VARIABLE} used across agent prompts so the runner knows what to ask for at execution time.

How to submit

The submission process uses GitHub pull requests:

1. Fork the marketplace repo. Go to github.com/mentiko/marketplace and fork it to your account.
2. Add your chain to the right category folder. The repo is organized by category: chains/content/, chains/engineering/, chains/research/, and so on. Drop your chain.json in the matching folder. Name the folder after your chain: chains/content/seo-blog-pipeline/.
3. Include a README. Every submission needs a README.md in the chain folder with four sections:
   • Description -- what the chain does and why it's useful.
   • Use case -- a concrete scenario where you'd run this chain.
   • Requirements -- any external APIs, models, or tools the chain depends on.
   • Example output -- a sample of what the chain produces when it runs.
4. Open a PR. Use this title format: [Chain] Your Chain Name. For agents or templates, use [Agent] or [Template] instead. In the PR body, include a screenshot or log snippet from a successful run.
5. Wait for review. The Mentiko team reviews marketplace submissions within 48 hours. We check for schema validity, prompt quality, and basic functionality. If something needs changes, we'll comment on the PR.

Best practices

These aren't requirements, but they'll make your chain more useful and more likely to get featured:

• Use descriptive agent names. keyword-researcher tells users what the agent does. agent1 tells them nothing. Name agents after their role in the pipeline.
• Include variable substitution for customization. The more parameterized your chain is, the more contexts it works in. A blog writer that hardcodes "write 1500 words" is less useful than one that accepts {WORD_COUNT}.
• Document expected inputs and outputs. State clearly what variables need to be set and what the final output looks like. Users shouldn't have to read every prompt to understand what they're getting.
• Keep chains focused. A chain should do one thing well. A "research and write a blog post" chain is good. A "research, write, publish, schedule social media, and send an email newsletter" chain is trying to do too much. Break large workflows into composable chains.
• Include error handling agents where appropriate. For chains that call external APIs or process unpredictable input, add a recovery agent that triggers on error events. This turns a fragile chain into a resilient one.
• Test with different inputs. Run your chain with edge cases before submitting. What happens with a very long topic? An empty variable? A topic in a different language? The more robust your chain, the fewer issues users will file.

Licensing

All marketplace submissions are released under the MIT license. This means anyone can use, modify, and redistribute your chain. You retain authorship credit -- your name stays on the chain and in the git history. Mentiko may feature your chain on the website, in blog posts, or in onboarding materials.

By submitting, you confirm that the chain is your original work (or that you have the right to share it) and that it doesn't include API keys, passwords, or other secrets.

Start building

The marketplace is only as good as what the community puts into it. If you've built a chain that solves a real problem, submit it. Someone else is probably trying to solve the same thing.

Browse the current marketplace at mentiko.com/marketplace, or go straight to the marketplace repo to submit your first chain.