开发者工具1 week ago
DocNova - Intelligent Documentation Platform for Developer Teams
通过 AI 辅助写作，从 API 规范和文档生成品牌化的开发者门户
@jitendraballa · X
完整作品展
技术栈
31 projects
通过 AI 辅助写作，从 API 规范和文档生成品牌化的开发者门户
@jitendraballa · X
用可视化编辑器设计、测试和发布AI就绪的API。
@milonspace · X
A specification nobody can find is functionally the same as no specification.
免费验证、修复、格式化 JSON 和 XML；监控 API 响应变化。
@SupportFixzi · X
Building an API monitoring tools which allows you to know when your AI breaks, before your users do. It has an API monitoring tool and an AI schema validator in it. This is a solution that can ensure your customers trust your app.
为开发者提供比Claude更快、更便宜的AI API平台。
@WebWrightAI · X
统一API网关，审计Token消耗并分析多个AI提供商的成本。
@amiuchat · X
我做了一个桌面工具：Token Switch。 给 Codex / Claude Code / OpenCode 重度用户统一管理 Provider、模型、Token、Base URL、连通测试和消耗统计。 多个 Agent，一个 Token 工作台。欢迎试用，也欢迎吐槽你最烦的配置问题。
监控 AI API 中转站实时健康状态和网关推荐，对比性能指标。
yaojingang · GitHub
TokHub AI API 中转站监控、推荐运营与 OpenAI 兼容专属网关系统，支持分层探测、健康评分、用量计量、告警审计和 Docker 自托管。
在Solana主网上创建SPL代币，支持IPFS存储和钱包签名，60秒内完成。
@SolanaForgeApp · X
Lovable Build is insane. 🚀 @Lovable turns ideas into real products faster than ever. Built with Lovable: — create Solana tokens easily. Describe. Build. Launch. ⚡
批量提交URLs至Google和Bing搜索索引，追踪AI引用。
@AjayGB4 · X
在GitHub pull requests上自动生成代码文档。
Aldasams · HN
Show HN: DocFlow – AI documentation updates for GitHub pull requests
通过稳定专线直接访问 Claude Fable-5 模型，提供透明定价。
@iveyzen · X
鹿友AI上线了 最贵的AI中转站，只因为想创造稳定fable-5访问专线
通过测试对比AI API中转站的性能、价格和模型纯度。
OkkMax — AI API 中转站评测与监测工具，聚合模型纯度、在线率、延迟、价格、用户点评和福利活动 - [更多介绍](https://github.com/fanbidog/okkmax-web)
可嵌入的可视化工作流编辑器，支持AI驱动或纯逻辑设计。
tahazsh · HN
Hi! I’m Taha. In many agentic products that support workflows (including one I worked on), I noticed they either don’t support node-based editors, or use React Flow and go through the difficult work of integrating it into their product to run it and work with their existing logic. So I thought about creating a tool that could help with this by closing the gap between the editor and the runtime. That’s why I created Wayflow. The basic architecture is simple: you just need to create a graph (which is a JSON object) that the runtime knows how to run. The runtime doesn’t care where that graph is coming from, it just needs the right schema. And with the help of the editor, you can create the graph, and then export it or directly save it on your backend in your database. And then when you want to execute it, you just hand it to the runtime. The runtime can either stream the execution (which is useful for the editor), or give you the final result. How you execute the graph is up to you: t