RRepoGEO

REPOGEO REPORT · LITE

bestruirui/octopus

Default branch dev · commit b7b053e7 · scanned 5/11/2026, 2:02:20 AM

GitHub: 2,108 stars · 264 forks

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 bestruirui/octopus, 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 README's core purpose statement for LLM API aggregation

    Why:

    CURRENT
    The current README starts with `### Octopus` followed by a tagline.
    COPY-PASTE FIX
    Modify the README to include a direct statement of purpose immediately after the H1, for example:
```
<div align="center">

### Octopus

Octopus is a self-hosted LLM API aggregation and load balancing service.

**A Simple, Beautiful, and Elegant LLM API Aggregation & Load Balancing Service for Individuals**

 English | [简体中文](README_zh.md)

</div>
```
  • mediumabout#2
    Add a homepage URL to the repository's 'About' section

    Why:

    COPY-PASTE FIX
    Set the homepage URL in the repository's 'About' section to `https://github.com/bestruirui/octopus` (or a dedicated project site if one exists).
  • lowreadme#3
    Consider adding a 'Comparison' or 'FAQ' section to the README

    Why:

    COPY-PASTE FIX
    Add a new section to the README, such as 'Comparison with Alternatives' or 'FAQ', to explicitly address how Octopus stands out from or relates to other LLM API gateways like LiteLLM or OpenAI Proxy.

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 bestruirui/octopus
Avg rank
—
Lower is better. #1 = top recommendation.
Share of voice
0%
Of all named tools, what % are you?
Top rival
LiteLLM
Recommended in 2 of 2 queries
COMPETITOR LEADERBOARD
  1. LiteLLM · recommended 2×
  2. OpenAI Proxy (Self-Hosted) · recommended 1×
  3. Portkey.ai (Self-Hosted) · recommended 1×
  4. LangChain · recommended 1×
  5. FastAPI · recommended 1×
  • CATEGORY QUERY
    How can I unify multiple large language model APIs and manage keys from one self-hosted service?
    you: not recommended
    AI recommended (in order):
    1. OpenAI Proxy (Self-Hosted)
    2. LiteLLM
    3. Portkey.ai (Self-Hosted)
    4. LangChain
    5. FastAPI
    6. Flask
    7. HashiCorp Vault
    8. AWS Secrets Manager
    9. Azure Key Vault

    AI recommended 9 alternatives but never named bestruirui/octopus. This is the gap to close.

    Show full AI answer
  • CATEGORY QUERY
    Looking for a self-hosted solution to load balance AI model requests and track usage costs.
    you: not recommended
    AI recommended (in order):
    1. OpenAI Proxy
    2. LiteLLM
    3. Nginx
    4. HAProxy
    5. Kong Gateway
    6. Caddy

    AI recommended 6 alternatives but never named bestruirui/octopus. 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 bestruirui/octopus?
    pass
    AI named bestruirui/octopus explicitly

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

  • If a team adopts bestruirui/octopus in production, what risks or prerequisites should they evaluate first?
    pass
    AI named bestruirui/octopus 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 bestruirui/octopus solve, and who is the primary audience?
    pass
    AI named bestruirui/octopus 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 bestruirui/octopus. 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/bestruirui/octopus.svg)](https://repogeo.com/en/r/bestruirui/octopus)
HTML
<a href="https://repogeo.com/en/r/bestruirui/octopus"><img src="https://repogeo.com/badge/bestruirui/octopus.svg" alt="RepoGEO" /></a>
Pro

Subscribe to Pro for deep diagnoses

bestruirui/octopus — 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
bestruirui/octopus — RepoGEO report