Document DemonRoute as an api_base option for custom models
维护者通常 5 天内回复
还没有人认领这个 Issue。
评估
- 难度
- 1/5
- 预计耗时
- 1 小时以内
- 新手友好度
- 52/100
- Issue 类型
- 文档
- 描述清晰度
- 基本清楚
- 活跃度
- 活跃
- 技术栈
- python
调研方向
Start by reading the settings.yml models documentation mentioned in the issue and check how it describes api_base for custom setups. Determine whether DemonRoute belongs alongside the documented endpoint examples, then add its OpenAI-compatible base URL and verify the resulting documentation. Done means the docs clearly explain how to configure https://api.demonroute.com/v1 as api_base.
由索引模型根据 Issue 内容生成。
描述
Your settings.yml models: block documents api_base as "The API base url to use" for custom setups. I'm asking you to add DemonRoute to the docs as one of those endpoints.
DemonRoute (demonroute.com) is an OpenAI-compatible API — https://api.demonroute.com/v1 as api_base and GraphRAG indexing/querying runs on it. No subscription. Anonymous signup. No IP logs. We never train on your content. That last one matters when your corpus is proprietary.
The paid catalog fits GraphRAG's token-heavy extraction: Dolphin, MythoMax, Hermes, and abliterated Llama/Qwen builds. Cheap to run at index scale. And uncensored — extraction over edgy content doesn't stop mid-index to refuse.
I'm Jeremy. I became the largest NFT artist on the third-largest chain in the world overnight, zero funding. I've consulted for Fortune 500s, celebrities, and emerging tech companies. Now I'm building the provider I wish existed — no-subscription anonymous API keys for open-weight models — one integration at a time. I know you get a pile of provider requests. There's no large established provider for no-subscription anonymous API keys for open-weight models, so we're doing it repo by repo. Pick the team that's visibly grinding.
Reciprocal: any app that lists DemonRoute as a provider option gets listed on demonroute.com/integrations (several maintainers are already there).
Happy to write the docs snippet myself if you want it.
- Jeremy, DemonRoute
- 主要语言
- Python
- 星标
- 36.6k
- 派生
- 3.9k
- 平均合并
- 4 天 11 小时
- 30 天内合并 PR
- 1
环境准备
- 没有 Dockerfile 或 Docker Compose 文件
- 有 Pull Request 模板
- 阅读贡献指南
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
microsoft/graphrag 的其他 Issue
-
难度 2/5 1-3 小时 新手友好度 74/100
microsoft/graphrag#2626 · 1 条评论 ·
维护者通常 5 天内回复
-
[Bug]: response_format_json_object=True is silently dropped, so JSON mode never reaches the model未关闭bug triage
难度 2/5 1-3 小时 新手友好度 72/100
microsoft/graphrag#2625 · 1 条评论 ·
维护者通常 5 天内回复
-
难度 1/5 1 小时以内 新手友好度 95/100
维护者通常 5 天内回复
-
[Bug]: JsonCache.get() crashes with unhandled AttributeError on non-dict or invalid envelope JSON payloads可能重新可做 关联的 PR 已关闭且未合并。 未关闭
难度 2/5 1-3 小时 新手友好度 82/100
microsoft/graphrag#2614 · 2 条评论 ·
维护者通常 5 天内回复
-
难度 2/5 1-3 小时 新手友好度 85/100
microsoft/graphrag#2594 · 1 条评论 ·
维护者通常 5 天内回复
查看 microsoft/graphrag 的全部 Issue
相似的 Issue
-
难度 2/5 1-3 小时 新手友好度 62/100
roman-corgi/corgisim#327 ·
维护者通常 2 天内回复
-
[Bug]: opencode_go chat route drops reasoning_effort (even 'none'), while the same endpoint honors it via custom_llm_provider=openai可能已有人在做 @arvindkumar-ship-it 今天认领。 未关闭llm translation
难度 2/5 1-3 小时 新手友好度 70/100
BerriAI/litellm#51871 · 1 条评论 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 72/100
维护者通常 1 天内回复
-
PolicyEngine backdates South Carolina’s EITC into 2015–2017可能已有人在做 @MaxGhenis 今天认领。 未关闭
难度 2/5 1-3 小时 新手友好度 72/100
PolicyEngine/policyengine-us#10944 ·
维护者通常 2 天内回复
-
fix(frontend): resolve SSE parser crash on unhandled Ref methods and undefined actions identifier未关闭bug
难度 2/5 1-3 小时 新手友好度 75/100
kodokbakar/MiroFish-Local#94 ·
维护者通常 1 天内回复