RRepoGEO

REPOGEO REPORT · LITE

zzsting88/relayAPI

Default branch main · commit 31a366a2 · scanned 5/22/2026, 3:17:28 AM

GitHub: 1,495 stars · 75 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
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 zzsting88/relayAPI, 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
    Clarify the README's opening statement to explicitly state the repo's purpose

    Why:

    CURRENT
    The README starts with "# AI API中转站推荐与评测" followed by "## 写在前面的话".
    COPY-PASTE FIX
    Insert the following sentence immediately after the H1: "本仓库旨在提供一个全面的AI API中转站推荐与评测平台，帮助开发者评估和选择稳定、价格合理且模型覆盖广泛的服务。"
  • hightopics#2
    Add relevant topics to the repository

    Why:

    CURRENT
    (none)
    COPY-PASTE FIX
    ai-api, api-proxy, ai-relay, llm-api, api-evaluation, service-comparison, pricing-guide, stability-testing, model-coverage, generative-ai
  • highlicense#3
    Add a license file to the repository

    Why:

    CURRENT
    (no LICENSE file detected)
    COPY-PASTE FIX
    Create a `LICENSE` file in the root directory with the MIT License text.

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 zzsting88/relayAPI
Avg rank
—
Lower is better. #1 = top recommendation.
Share of voice
0%
Of all named tools, what % are you?
Top rival
Azure AI Studio / Azure OpenAI Service
Recommended in 2 of 2 queries
COMPETITOR LEADERBOARD
  1. Azure AI Studio / Azure OpenAI Service · recommended 2×
  2. Google Cloud Vertex AI · recommended 2×
  3. Portkey.ai · recommended 2×
  4. OpenAI API · recommended 1×
  5. Anthropic API · recommended 1×
  • CATEGORY QUERY
    Where can I find reliable and stable AI API proxy services for developers?
    you: not recommended
    AI recommended (in order):
    1. OpenAI API
    2. Azure AI Studio / Azure OpenAI Service
    3. Google Cloud Vertex AI
    4. Anthropic API
    5. LiteLLM (BerriAI/litellm)
    6. Portkey.ai
    7. OpenRouter.ai

    AI recommended 7 alternatives but never named zzsting88/relayAPI. This is the gap to close.

    Show full AI answer
  • CATEGORY QUERY
    How to evaluate AI model relay providers for stability, pricing, and model coverage?
    you: not recommended
    AI recommended (in order):
    1. Anyscale Endpoints
    2. Fireworks AI
    3. OpenRouter
    4. Together AI
    5. Azure AI Studio / Azure OpenAI Service
    6. Google Cloud Vertex AI
    7. Portkey.ai

    AI recommended 7 alternatives but never named zzsting88/relayAPI. 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 zzsting88/relayAPI?
    pass
    AI named zzsting88/relayAPI explicitly

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

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

Subscribe to Pro for deep diagnoses

zzsting88/relayAPI — 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