Add DemonRoute as a custom endpoint option

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

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
2/5
Tiempo estimado
1-3 horas
Aptitud para principiantes
22/100
Tipo de issue
Nueva funcionalidad
Claridad
Bastante claro
Estado de actividad
Activo
Área
documentation

Línea de trabajo

This is a vendor request to list a third-party OpenAI-compatible endpoint, not a described code defect; it needs a maintainer decision on whether the project endorses external providers before any edit happens. The only concrete hook is the existing OPENAI_API_ENDPOINT setting, so the first step is to find where that variable is documented and whether an example config already exists for alternate endpoints. Done means a maintainer has approved the listing and the docs/example config places the new base URL next to the existing endpoint guidance.

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

Descripción

Hi. I run DemonRoute — an anonymous, no-subscription API key service for open-weight models. No training on your data, no IP logs, no cookies. You bring your own key and point at any OpenAI-compatible endpoint.

Your action already takes a custom endpoint through OPENAI_API_ENDPOINT. That means DemonRoute drops in with one env change: base URL https://api.demonroute.com/v1, your key, and a model id. No code changes on your side.

Why it fits here: code review runs on every PR, so per-PR cost adds up fast. DemonRoute carries uncensored fine-tunes you will not find on the big routers — Dolphin, MythoMax, Hermes, abliterated Llama and Qwen builds, and uncensored writing fine-tunes. Teams that review a lot of code get a cheaper backend without giving up model choice.

I am not asking you to do the work. I will write the docs change or the example config myself if you point me at the right file. Projects that list DemonRoute get listed back on demonroute.com/integrations — traffic goes both ways. Other projects already shipping it are listed there.

Quick background, since there are a lot of gateway pitches out there: I am Jeremy Ryan. During the NFT peak I became the largest NFT artist on the third-largest chain in the world — overnight, with zero funding. That turned into consulting for Fortune 500 companies, celebrities, and emerging tech companies, all on my name and the work behind it. I run several endeavors under NFT Demon Holdings LLC. DemonRoute is the one I am most passionate about, and it is the one I am building repo by repo. You are not betting on an endpoint. You are betting on me.

Happy to answer questions or draft the change. Just tell me where it belongs.

— Jeremy, DemonRoute

Lenguaje dominante
JavaScript
Estrellas
4.5k
Forks
469
Sin PR fusionados en 30 d

Preparar el entorno

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 anc95/ChatGPT-CodeReview

Todos los issues de anc95/ChatGPT-CodeReview

Issues similares

Más issues de JavaScript

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.