[REQUEST] 88API provider integration and ecosystem partnership

未關閉
#8,880 0 則留言 0 個 reaction 已指派 0 人 在 GitHub 檢視

維護者通常 1 天內回覆

還沒有人認領這個 Issue。

評估

難度
5/5
預估耗時
一週以上
新手友好度
12/100
Issue 類型
功能
描述清晰度
需要釐清
活躍度
活躍
領域
api

研究方向

This is a commercial partnership inquiry with no defined code change, so there is no file or test to start from. Maintainer input is needed first, on whether an 88API preset or documentation example fits Sim's provider setup, and whether the existing custom Base URL route in #801, #635 and #1579 is enough. Done would be a recorded maintainer decision on that, not a patch.

由索引模型根據 Issue 內容生成。

描述

Is your feature request related to a problem? Please describe.

Sim supports many model providers and BYOK workflows, but users who want one OpenAI-compatible endpoint for models such as DeepSeek, Qwen, Kimi, GLM, and MiniMax do not currently have a documented 88API provider path or preset.

I found the existing custom endpoint requests in #801, #635, and #1579. This proposal is related, but narrower: it asks whether an optional 88API provider integration or a verified configuration example would be useful. It is not a request to replace any existing provider.

Describe the solution you'd like

We are 88API (https://88api.ai/), a multi-model API service. We would like to ask whether the Sim maintainers are open to evaluating one of these non-exclusive options:

  • validate 88API through Sim's existing OpenAI-compatible or custom endpoint path;
  • add an optional 88API provider preset or configuration documentation, if that fits Sim's provider architecture;
  • test compatibility using API credits and technical support supplied by 88API;
  • offer capped introductory credits to Sim users;
  • discuss sponsorship or another ecosystem partnership format, if Sim accepts commercial partnerships.

We can provide test credentials and work through compatibility issues before any documentation or integration is considered. We are not asking the project to make unverified performance or compatibility claims.

If commercial or provider partnership inquiries are handled outside GitHub, please point us to the appropriate public contact channel.

Describe alternatives you've considered

Generic custom Base URL support, as discussed in #801 and #635, may already provide a sufficient technical route. If so, a tested documentation example could be enough and a dedicated provider block may not be necessary.

Additional context

Disclosure: this is a commercial provider integration and ecosystem partnership inquiry from 88API.

Website: https://88api.ai/

主要語言
TypeScript
星號
29.8k
分支
3.9k
平均合併
1 小時 44 分鐘
30 天內合併 PR
841

環境準備

這個專案沒有提供開發容器、Dockerfile 或貢獻指南,環境需要你自己搭建:先看它的 README,通用步驟見我們的新手貢獻指南。

從這裡開始

  1. 先讀完整個 Issue,再讀專案的貢獻指南。
  2. 在 Issue 下留言說明你要接手 —— 這能避免兩個人做同樣的事。
  3. Fork 儲存庫,在一個分支上完成修改。
  4. 送出 Pull Request,並在描述裡引用這個 Issue 編號。

simstudioai/sim 的其他 Issue

查看 simstudioai/sim 的全部 Issue

相似的 Issue

更多 TypeScript Issue

把新 issue 寄到你的電子郵件信箱

精選適合新手參與的 GitHub issue 摘要。