Skip to content

docs(readme): evolve supporter section into Sponsors section (sub2api-style) - #7799

Merged
diegosouzapw merged 1 commit into
release/v3.8.49from
docs/sponsors-section
Jul 19, 2026
Merged

diegosouzapw merged 1 commit into
release/v3.8.49from
docs/sponsors-section

Conversation

@diegosouzapw

Copy link
Copy Markdown
Owner

Summary

Evolves the Official Supporters section into a full Sponsors section, taking the best of the two reference formats (Wei-Shaw/sub2api and router-for-me/CLIProxyAPI) and adding what neither has:

  • "Want to appear here?" call-to-action with the maintainer contact and the audience pitch
  • Kimi entry in the sub2api thank-you format, selling the sponsor's product (K3: 1M context, native vision, works with Claude Code/Codex)
  • "Where the sponsorship goes:" explicit transparency label — release pipeline (merge validation powered by Kimi K3) + feature development
  • Shields badge in the official Kimi blue #1783FF, matching the dashboard provider-card accent shipped in feat(dashboard): pin Kimi providers first in category + official supporter card accent #7775
  • "Get a Moonshot API key →" CTA (plain link for now; becomes the disclosed partner tracking link when Kimi provides it)

Docs-only change on top of the section merged in #7770.

Refs: Kimi partnership pilot.

@gemini-code-assist

Copy link
Copy Markdown
Contributor

Warning

You have reached your daily quota limit. Please wait up to 24 hours and I will start processing your requests again!

@diegosouzapw
diegosouzapw merged commit f79a548 into release/v3.8.49 Jul 19, 2026
6 of 9 checks passed
@diegosouzapw
diegosouzapw deleted the docs/sponsors-section branch July 19, 2026 21:00
HouMinXi pushed a commit to HouMinXi/OmniRoute that referenced this pull request Aug 2, 2026
muhamadgalihsaputra pushed a commit to niyatna/NiyatnaRoute that referenced this pull request Sep 27, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant