[REQUEST] 88API provider integration and ecosystem partnership

Offen
  • Stimmt etwas nicht?
#8,880 0 Kommentare 0 Reaktionen 0 zugewiesene Personen Auf GitHub ansehen

Maintainer antworten meist innerhalb von 1 Tag

Dieses Issue hat noch niemand übernommen.

Bewertung

Schwierigkeit
5/5
Geschätzter Aufwand
Über eine Woche
Anfängerfreundlichkeit
12/100
Issue-Typ
Feature
Klarheit
Muss geklärt werden
Aktivitätsstatus
Aktiv
Bereich
api

Rechercherichtung

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.

Vom Indexierungsmodell aus dem Issue-Text verfasst.

Beschreibung

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/

Vorherrschende Sprache
TypeScript
Sterne
29.8k
Forks
3.9k
Ø Merge
1 Std. 44 Min.
Gemergte PRs (30 T.)
841

Entwicklungsumgebung

Dieses Projekt bietet weder Dev-Container noch Dockerfile noch Beitragsleitfaden – die Einrichtung liegt bei Ihnen. Beginnen Sie mit der README; die allgemeinen Schritte stehen in unserem Leitfaden für den ersten Beitrag.

Erste Schritte

  1. Lesen Sie das ganze Issue und danach den Beitragsleitfaden des Projekts.
  2. Schreiben Sie ins Issue, dass Sie es übernehmen — das erspart doppelte Arbeit.
  3. Forken Sie das Repository und arbeiten Sie in einem Branch.
  4. Öffnen Sie einen Pull Request, der die Issue-Nummer nennt.

Mehr aus simstudioai/sim

Alle Issues in simstudioai/sim

Ähnliche Issues

Weitere Issues zu TypeScript

Neue Issues direkt in Ihr Postfach

Eine kurze Übersicht über anfängerfreundliche GitHub-Issues.