Skip to main content
Navigate the review process with confidence. This guide shows you how to prepare your agent for a higher chance of approval.

I. Content Review Criteria

1. Agent Name

Requirements:
  • Clearly conveys the agent’s core functionality or key value proposition
  • Must not be vague or meaningless
  • Must not contain advertisements, contact information, or unlicensed brand names
Examples (Rejection):
  • AI Tools
  • Gernel Voice AI Agent
  • DO NOT Open

2. Overview (One-Sentence Summary)

Requirements:
  • Clearly states what the agent does in one sentence
  • Enables users to instantly grasp its value
Example (Approved):
  • “An AI writing assistant that auto-generates SEO-friendly blog posts.”
Example (Rejection):
  • “A very powerful writing tool.” (Too vague)

3. Description (Detailed Description)

Must Include All of the Following:
  • Target users (e.g., “Ideal for content creators”)
  • Use cases (e.g., “Writing WeChat official accounts or Xiaohongshu captions”)
  • Key functionalities
  • Output format (e.g., “Generates an 800-word blog post + image suggestions”)
Rejection Criteria:
  • Missing any of the above elements
  • Contains external links that redirect users off-platform
  • Excessively long (>100 words). (Note: Most current agents are image-generation focused and do not require lengthy explanations.)

4. Advantages

Requirements:
  • Presented as bullet points
  • Each point highlights a distinct, non-generic advantage
Examples (Approved):
  • ✔️ One-click publishing across multiple platforms
  • ✔️ Auto-generates titles and SEO keywords
Examples (Rejection):
  • “Intelligent and efficient”
  • “Great user experience” (Too vague/boilerplate)

5. Key Features

Requirements:
  • Bullet-point format, ordered by importance
  • Specific, tangible capabilities — no abstract concepts
Examples (Approved):
  • ✔️ Input a topic → outputs a complete blog post
  • ✔️ Supports bilingual output (Chinese/English)
Examples (Rejection):
  • “Powerful AI engine”
  • “Intelligent analytical capability”

6. Prompts (Usage Guidance)

Requirements:
  • Instructs users on how to phrase inputs for optimal results
  • Provides concrete examples (e.g., “Input: ‘I want to write an article about running.’”)
Rejection if:
  • Left blank or only says “Please enter content.”

7. Showcase / Cover Image

Requirements:
  • Clearly displays the agent’s actual output
  • No irrelevant stock images, placeholders, or excessive watermarks
  • Supports aspect ratios: 1:1 and 16:10
  • Resolution ≥ 512×512 px
Examples (Rejection):
  • Blurry screenshots with unreadable text
  • Unauthorized or functionally irrelevant images

II. Safety Review

All content must comply with the following: ❌ No explicit, pornographic, or violent content ❌ No references to politics, religion, or sensitive events ❌ No privacy violations, fraud inducement, or false advertising ❌ No covert promotion (e.g., unsolicited links to Discord, X/Twitter, Facebook, or external websites)
Note: External references (e.g., cited sources) are acceptable if necessary for context — but aggressive self-promotion or personal contact info is prohibited.

III. Experience Evaluation Criteria

1. Language Consistency

Input LanguageRequired Output LanguageAllowed Internal Processing Language(s)
ChineseChineseChinese or English
EnglishEnglishEnglish only
Japanese, Spanish, Portuguese, French, German, KoreanMust match input languageEnglish or the same target language
⚠️ Rejection if:
  • Unjustified language mixing (e.g., English input → Chinese output)

2. Functional Availability

File Upload Support

Format TypeExamplesRequired?
Common formats✅ JPG, PNG, WebP, JPEGMandatory
Newer formats✅ GIF, AVIFOptional (recommended)
Special formatsSVG, PDF, HEICOptional (recommended)
⚠️ Rejection if:
  • Claims image processing support but fails on PNG/JPG

Output File Download

  • Generated images, PDFs, videos, etc., must be downloadable
  • Verification: Click “Download” → confirm successful file save
Note: As long as users can access/retrieve the output, the requirement is satisfied.

Clickable Output URLs

  • All links must be functional and lead to valid, safe destinations
  • Must not be broken (e.g., http://error) or redirect to malicious/blacklisted sites

3. Ease of Use

User input requirements must be reasonable:
Input TypeAcceptableUnacceptable
File Upload1–5 imagesRequiring ≥15 images
Text Input50–200 wordsRequiring ≥500 words
Multi-turn Dialog3–5 rounds maxForcing ≥8 rounds before output
⚠️ Rejection if:
  • Entry barrier is excessively high, harming UX
  • Requires users to manually edit/Photoshop input images

4. Minimum Output Quality

Output TypeQuality Requirements
Text
  • No severe hallucinations (e.g., fabricating non-existent facts)
  • No common-sense violations
  • Occasional keyword filtering is acceptable; frequent/systematic censorship leads to rejection
URLs
  • Links must be real and accessible
  • No mass generation of invalid or shortened links
Images
  • Resolution ≥ 512×512 px
  • Clear, coherent visuals; minimal artifacts/distortions
  • Artistic nudity permitted (e.g., classical sculptures); explicit sexual content prohibited
  • For outfit-transfer agents: approve if changes are imperceptible (within 10% difference) or visually ambiguous
  • ❌ Reject: cropped/incomplete outputs or severely blurred images
Videos
  • No glaring physical/logical errors (e.g., walking upside-down)
  • Smooth playback; no stuttering or frame tearing

IV. Common Rejection Cases

  • Issue Type: ❌ Vague Information
    • Example: Name: “Smart Writing Tool” — no specific functionality described
  • Issue Type: ❌ Language Inconsistency
    • Example: English input → full Chinese output
  • Issue Type: ❌ Missing Functionality
    • Example: Claims “PDF parsing supported”, but upload fails with error
  • Issue Type: ❌ Low-Quality Output
    • Example: Generated image: 256×256, blurry
  • Issue Type: ❌ Safety Violation
    • Example: Showcase image contains politically sensitive symbols
  • Issue Type: ❌ Covert Promotion
    • Example: Output includes: “Add me on Telegram: xxx”
  • Issue Type: ❌ Insufficient Runtime Stability
    • Requirement: Each submitted version must have 5 consecutive successful runs before UTC 23:59 on the day of submission
    • Example 1: New version has only 3 successful runs → Rejected
    • Example 2: New version has 5 runs but only 4 successful and 1 failed → Rejected (runs must be consecutive)