[REQUEST] 88API provider integration and ecosystem partnership

Ouverte
  • Quelque chose ne va pas ?
#8,880 0 commentaires 0 réactions 0 personnes assignées Voir sur GitHub

Les mainteneurs répondent en général sous 1 jour

Personne n'a encore pris cette issue.

Évaluation

Difficulté
5/5
Temps estimé
Plus d'une semaine
Accessibilité débutants
12/100
Type d'issue
Fonctionnalité
Clarté
À clarifier
Activité
Active
Domaine
api

Piste de recherche

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.

Rédigé par le modèle d'indexation à partir du texte de l'issue.

Description

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/

Langage dominant
TypeScript
Étoiles
29.8k
Forks
3.9k
Merge moyen
1 h 44 min
PR mergées (30 j)
841

Préparer son environnement

Ce projet ne fournit ni conteneur de développement, ni Dockerfile, ni guide de contribution : l'installation est à votre charge. Commencez par son README, et consultez notre guide de la première contribution pour les étapes générales.

Par où commencer

  1. Lisez l'issue en entier, puis le guide de contribution du projet.
  2. Signalez en commentaire que vous la prenez — cela évite que deux personnes fassent le même travail.
  3. Forkez le dépôt et travaillez sur une branche.
  4. Ouvrez une pull request qui référence le numéro de l'issue.

Autres issues de simstudioai/sim

Toutes les issues de simstudioai/sim

Issues similaires

Plus d'issues TypeScript

Recevez les nouvelles issues par e-mail

Un résumé court des issues GitHub adaptées aux débutants.