RRepoGEO

REPOGEO REPORT · LITE

64bit/async-openai

Default branch main · commit eeb375f3 · scanned 5/19/2026, 7:02:06 PM

GitHub: 1,889 stars · 370 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
33 /100
Critical
Category recall
0 / 2
Not recommended in any query
Rule findings
2 pass · 0 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 64bit/async-openai, 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 introductory paragraph to highlight key features

    Why:

    CURRENT
    <p align="center"> Async Rust library for OpenAI </p>
    COPY-PASTE FIX
    <p align="center"> A comprehensive, asynchronous Rust client for the OpenAI API, featuring streaming, exponential backoff retries, and first-class support for Azure OpenAI Service. </p>
  • hightopics#2
    Expand repository topics to include key features and specific use cases

    Why:

    CURRENT
    openai, rust
    COPY-PASTE FIX
    openai, rust, async, llm, azure, streaming, api-client, openai-api, large-language-models
  • mediumabout#3
    Enhance the repository description to be more specific about its capabilities

    Why:

    CURRENT
    Rust library for OpenAI
    COPY-PASTE FIX
    Asynchronous Rust client for OpenAI API, offering streaming, exponential backoff retries, and Azure compatibility.

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 64bit/async-openai
Avg rank
—
Lower is better. #1 = top recommendation.
Share of voice
0%
Of all named tools, what % are you?
Top rival
reqwest
Recommended in 2 of 2 queries
COMPETITOR LEADERBOARD
  1. reqwest · recommended 2×
  2. isahc · recommended 2×
  3. openai-rust · recommended 1×
  4. llm · recommended 1×
  5. surf · recommended 1×
  • CATEGORY QUERY
    What's a robust asynchronous library for connecting to large language model APIs in Rust?
    you: not recommended
    AI recommended (in order):
    1. reqwest
    2. openai-rust
    3. llm
    4. isahc
    5. surf

    AI recommended 5 alternatives but never named 64bit/async-openai. This is the gap to close.

    Show full AI answer
  • CATEGORY QUERY
    Seeking a Rust client for AI services with streaming, retry logic, and Azure compatibility.
    you: not recommended
    AI recommended (in order):
    1. reqwest
    2. tokio
    3. futures-retry
    4. azure_core
    5. azure_ai_openai
    6. isahc
    7. ureq
    8. retry
    9. hyper

    AI recommended 9 alternatives but never named 64bit/async-openai. This is the gap to close.

    Show full AI answer

Objective checks

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

  • Metadata completeness
    pass

  • 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 64bit/async-openai?
    pass
    AI named 64bit/async-openai explicitly

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

  • If a team adopts 64bit/async-openai in production, what risks or prerequisites should they evaluate first?
    pass
    AI named 64bit/async-openai 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 64bit/async-openai solve, and who is the primary audience?
    pass
    AI did not name 64bit/async-openai — 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?

Embed your GEO score

Drop this badge into the README of 64bit/async-openai. 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/64bit/async-openai.svg)](https://repogeo.com/en/r/64bit/async-openai)
HTML
<a href="https://repogeo.com/en/r/64bit/async-openai"><img src="https://repogeo.com/badge/64bit/async-openai.svg" alt="RepoGEO" /></a>
Pro

Subscribe to Pro for deep diagnoses

64bit/async-openai — 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