[REQUEST] 88API provider integration and ecosystem partnership

Abierto
  • ¿Algo no está bien?
#8,880 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
5/5
Tiempo estimado
Más de una semana
Aptitud para principiantes
12/100
Tipo de issue
Nueva funcionalidad
Claridad
Necesita aclaración
Estado de actividad
Activo
Área
api

Línea de trabajo

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.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

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/

Lenguaje dominante
TypeScript
Estrellas
29.8k
Forks
3.9k
Merge medio
1 h 44 min
PR fusionados (30 d)
841

Preparar el entorno

Este proyecto no incluye contenedor de desarrollo, Dockerfile ni guía de contribución, así que la configuración corre por tu cuenta: empieza por su README y consulta nuestra guía para la primera contribución para los pasos generales.

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de simstudioai/sim

Todos los issues de simstudioai/sim

Issues similares

Más issues de TypeScript

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.