RRepoGEO

REPOGEO REPORT · LITE

Soju06/codex-lb

Default branch main · commit 17c1762d · scanned 6/23/2026, 2:02:14 AM

GitHub: 2,006 stars · 311 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)

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

AI VISIBILITY SCORE
28 /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
2 / 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 Soju06/codex-lb, 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 H1 to specify AI API load balancing

    Why:

    CURRENT
    # codex-lb

Load balancer for ChatGPT accounts. Pool multiple accounts, track usage, manage API keys, view everything in a dashboard.
    COPY-PASTE FIX
    # codex-lb: AI API Load Balancer for ChatGPT & OpenAI Accounts

Pool multiple ChatGPT/OpenAI accounts, track usage, manage API keys, and view everything in a dashboard.
  • mediumreadme#2
    Explicitly state the tech stack in the README's opening

    Why:

    COPY-PASTE FIX
    Built with Python and FastAPI, codex-lb provides a robust and scalable solution for managing your AI API access.
  • lowreadme#3
    Add a dedicated comparison section to the README

    Why:

    COPY-PASTE FIX
    ## Why choose codex-lb?

Unlike generic API gateways or general-purpose load balancers, codex-lb is purpose-built for managing multiple ChatGPT and OpenAI API accounts. It offers integrated usage tracking, API key management with rate limits, and a user-friendly dashboard, specifically tailored for AI API access.

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 Soju06/codex-lb
Avg rank
—
Lower is better. #1 = top recommendation.
Share of voice
0%
Of all named tools, what % are you?
Top rival
Apigee
Recommended in 2 of 2 queries
COMPETITOR LEADERBOARD
  1. Apigee · recommended 2×
  2. AWS API Gateway · recommended 2×
  3. OpenRouter · recommended 1×
  4. LiteLLM · recommended 1×
  5. Helicone · recommended 1×
  • CATEGORY QUERY
    How can I pool multiple generative AI accounts and track their combined usage?
    you: not recommended
    AI recommended (in order):
    1. OpenRouter
    2. LiteLLM
    3. Helicone
    4. Langfuse
    5. Azure AI Studio
    6. Google Cloud Vertex AI
    7. Kong Gateway
    8. Apigee
    9. AWS API Gateway
    10. Elasticsearch
    11. Kibana
    12. Datadog

    AI recommended 12 alternatives but never named Soju06/codex-lb. This is the gap to close.

    Show full AI answer
  • CATEGORY QUERY
    Need an API proxy to load balance across AI models with usage tracking and a web dashboard.
    you: not recommended
    AI recommended (in order):
    1. Kong Gateway (Kong/kong)
    2. Kong Manager
    3. Kuma (kumahq/kuma)
    4. Apigee
    5. AWS API Gateway
    6. Tyk API Gateway (TykTechnologies/tyk)
    7. Tyk Dashboard
    8. Nginx (nginx/nginx)
    9. Nginx Plus
    10. Envoy Proxy (envoyproxy/envoy)

    AI recommended 10 alternatives but never named Soju06/codex-lb. 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 Soju06/codex-lb?
    pass
    AI did not name Soju06/codex-lb — likely talking about a different project

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

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

Subscribe to Pro for deep diagnoses

Soju06/codex-lb — 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