RRepoGEO

REPOGEO REPORT · LITE

remsky/Kokoro-FastAPI

Default branch master · commit c5ccfa18 · scanned 6/27/2026, 1:52:21 AM

GitHub: 5,073 stars · 840 forks

Scan history for this repo

Score trend below includes all ready runs (older left, newer right; scroll horizontally if needed). The table is collapsed by default—expand for newest-first rows, 10 per page.

Score trend (left → right: older → newer)

3 ready scans. Expand the table below for newest-first rows (10 per page, paginated).

AI VISIBILITY SCORE
35 /100
Critical
Category recall
0 / 2
Not recommended in any query
Rule findings
1 pass · 1 warn · 0 fail
Objective metadata checks
AI knows your name
3 / 3
Direct prompts that named your repo
HOW TO READ THIS REPORT

Action plan is what to do next — copy-pasteable changes prioritized by impact. Category visibility is the real GEO test: when a user asks an AI a brand-free question that should surface remsky/Kokoro-FastAPI, does the AI actually recommend you — or your competitors? Objective checks verify the metadata signals AI engines weight first. Self-mention check detects whether AI even knows you exist by name.

Action plan — copy-paste fixes

3 prioritized changes generated by gemini-2.5-flash. Mark items done after you ship the fix.

OVERALL DIRECTION
  • highreadme#1
    Reposition the README's primary heading to specify its TTS API purpose

    Why:

    CURRENT
    # <sub><sub>_`FastKoko`_ </sub></sub>
    COPY-PASTE FIX
    # FastKoko: OpenAI-Compatible FastAPI Text-to-Speech API for Kokoro-82M
  • highabout#2
    Refine the 'About' description to highlight its role as an OpenAI-compatible TTS API service

    Why:

    CURRENT
    Dockerized FastAPI wrapper for Kokoro-82M text-to-speech model w/multiplatform CPU, AMD, NVIDIA GPU PyTorch support, handling, and auto-stitching
    COPY-PASTE FIX
    An OpenAI-compatible FastAPI text-to-speech API service for the Kokoro-82M model, offering multi-language support and broad hardware compatibility (CPU, NVIDIA, AMD, Apple Silicon) via Docker.
  • mediumhomepage#3
    Add a homepage URL to the repository metadata

    Why:

    COPY-PASTE FIX
    https://huggingface.co/spaces/Remsky/FastKoko

Category GEO backends resolved for this scan: google/gemini-2.5-flash, deepseek/deepseek-v4-flash

Category visibility — the real GEO test

Brand-free queries asked to google/gemini-2.5-flash. Did AI recommend you, or someone else?

Same questions for every model — switch tabs to compare answers and rankings.

Recall
0 / 2
0% of queries surface remsky/Kokoro-FastAPI
Avg rank
—
Lower is better. #1 = top recommendation.
Share of voice
0%
Of all named tools, what % are you?
Top rival
OpenAI TTS API
Recommended in 1 of 2 queries
COMPETITOR LEADERBOARD
  1. OpenAI TTS API · recommended 1×
  2. ElevenLabs · recommended 1×
  3. Google Cloud Text-to-Speech · recommended 1×
  4. Amazon Polly · recommended 1×
  5. Microsoft Azure Text to Speech · recommended 1×
  • CATEGORY QUERY
    Need a text-to-speech service with an OpenAI-compatible API and multi-language support.
    you: not recommended
    AI recommended (in order):
    1. OpenAI TTS API
    2. ElevenLabs
    3. Google Cloud Text-to-Speech
    4. Amazon Polly
    5. Microsoft Azure Text to Speech

    AI recommended 5 alternatives but never named remsky/Kokoro-FastAPI. This is the gap to close.

    Show full AI answer
  • CATEGORY QUERY
    Seeking a dockerized text-to-speech solution with broad CPU and GPU hardware support.
    you: not recommended
    AI recommended (in order):
    1. Mozilla TTS
    2. Coqui TTS
    3. ESPnet
    4. NVIDIA Riva
    5. Tacotron 2 / WaveGlow (NVIDIA/DeepLearningExamples)

    AI recommended 5 alternatives but never named remsky/Kokoro-FastAPI. This is the gap to close.

    Show full AI answer

Objective checks

Rule-based audits of metadata signals AI engines weight most.

  • Metadata completeness
    warn

    Suggestion:

  • README presence
    pass

Self-mention check

Does AI even know your repo exists when asked about it directly?

  • Compared to common alternatives in this category, what is the core differentiator of remsky/Kokoro-FastAPI?
    pass
    AI named remsky/Kokoro-FastAPI explicitly

    AI answers can be confidently wrong. Read for accuracy: does it match your actual tech stack, audience, and differentiator?

  • If a team adopts remsky/Kokoro-FastAPI in production, what risks or prerequisites should they evaluate first?
    pass
    AI named remsky/Kokoro-FastAPI explicitly

    AI answers can be confidently wrong. Read for accuracy: does it match your actual tech stack, audience, and differentiator?

  • In one sentence, what problem does the repo remsky/Kokoro-FastAPI solve, and who is the primary audience?
    pass
    AI named remsky/Kokoro-FastAPI explicitly

    AI answers can be confidently wrong. Read for accuracy: does it match your actual tech stack, audience, and differentiator?

Embed your GEO score

Drop this badge into the README of remsky/Kokoro-FastAPI. It auto-updates whenever the report is rescanned and links back to the latest report — easy public proof that you care about AI discoverability.

RepoGEO badge previewLive preview
MARKDOWN (README)
[![RepoGEO](https://repogeo.com/badge/remsky/Kokoro-FastAPI.svg)](https://repogeo.com/en/r/remsky/Kokoro-FastAPI)
HTML
<a href="https://repogeo.com/en/r/remsky/Kokoro-FastAPI"><img src="https://repogeo.com/badge/remsky/Kokoro-FastAPI.svg" alt="RepoGEO" /></a>
Pro

Subscribe to Pro for deep diagnoses

remsky/Kokoro-FastAPI — Lite scans stay free; this card itemizes Pro deep limits vs Lite.

  • Deep reports10 / month
  • Brand-free category queries5 vs 2 in Lite
  • Prioritized action items8 vs 3 in Lite