最新资讯
dev.to 为 CI/CD 构建 AI 质量门禁 dev.to Kakao 发布面向 AI Agent 的决策模型 Kanana-2-v-decide computerworld.com Microsoft 对 Copilot Chat 企业用户扩大未公开的使用限制 pub.towardsai.net Google 发布 Gemini 4 Carbon:主打网络安全能力的前沿模型 gradientflow.com METR 研究:AI 正在加速构建 AI 的团队本身 www.infoq.com GitLab 19.5 将 Agentic 开发纳入 DevOps 平台的治理体系 aiacceleratorinstitute.com 研究:AI Agent 的复杂流程编排可能反而是问题所在 pub.towardsai.net MongoDB 推出 Vercel AI SDK 集成:为 AI 应用提供持久记忆 thenewstack.io Google 捐出被 Anthropic 和 OpenAI 使用的代码沙箱 gVisor,押注 AI Agent 基础设施开源 dev.to 在信任 AI 生成的测试用例前,如何逐条复核 unite.ai Franklin Templeton 构建 AI 研究工作流以揭示风险 techxplore.com AI 助力寻找更优的钛合金 3D 打印工艺参数
多元动态
登录 注册
大模型 dev.to · @yummy342

AI 引擎在回答 LLM 网关问题时实际引用了什么

原文 我的收藏

作者按开发者真实提问方式设计27个问题,于2026-09-20向四个引擎提问并统计引用指向。仅Perplexity(通过OpenRouter访问)返回答案来源,其余三个引擎因无引用链未纳入数据集。最终得到613条引用记录,去重后为569个唯一URL、346个唯一域名,作者称其中部分发现与自家产品策略相悖。

AI推荐理由 作者用27个开发者式提问在2026-09-20向四个引擎发问,仅Perplexity(经OpenRouter)返回引用来源,共得613条引用、569个唯一URL、346个唯一域名,并称部分结果与自家产品策略相悖。属小样本自测,非同行评审,结论外推需谨慎,但对LLM网关类内容的引用分布有参考价值。

62

正文

What AI engines actually cite when you ask about LLM gateways We wrote 27 questions the way a developer asks them, sent them to four engines on one day, and counted where the citations pointed. Here is the distribution — including the findings that argue against our own product strategy. What we did The 27 questions are the ones a developer actually types, not what a keyword tool suggests: What are the best OpenRouter alternatives? Is it safe to route API calls through a third-party LLM gateway? Are free LLM APIs reliable enough for real work? How do I point Claude Code at a different API base URL? Each question went to four engines on 2026-09-20. Only one of them returns the sources its answer was built from — Perplexity, reached through OpenRouter. An answer with no citation trail cannot be measured, so the other three engines are not in this dataset at all. What is left: 613 citation entries across the 27 answers, collapsing to 569 unique URLs and 346 unique domains. 1. No single source dominates The ten most-cited domains account for 18.6% of all citations. The remaining 81% spreads across 336 domains, and most of those appear exactly once. This is worth stating plainly, because the standard advice in this space — get into the big awesome list and you are done — does not survive contact with the data. There is no list to win. There is a long tail, and each entry in it is a small bet. 2. The head still has a shape Domain Citations What the cited pages actually are github.com 17 Awesome lists, tool repositories, and issue threads dev.to 17 Long-form tutorials and comparisons, first person openrouter.ai 15 A competitor's own product and pricing pages llmgateway.io 15 Comparison blog posts, pricing, and legal pages startupfortune.com 11 News coverage and tag archives marktechpost.com 10 Category index pages youtube.com 9 Tutorial videos reddit.com 3 Discussion threads The GitHub entries are not documentation. They are lists — directories of free APIs and gateways — and issue threads, where someone asks how to change the base URL in Claude Code or Cline and other people answer. Both are places where a project can be named without writing a blog post. The dev.to entries are all first-person and all contain numbers. Not one of them is a product announcement. And competitor marketing pages get cited directly — including, for the question about whether a gateway can read your prompts, a competitor's privacy policy and sub-processor list. Those pages are usually written for lawyers. They are being read as answers. 3. Reddit barely appears Three citations out of 613 — 0.5% — went to reddit.com. That one deserves a pause, because "Reddit shows up in 40% of AI answers" is repeated everywhere. The figure is real. It is also averaged across every topic imaginable. For developer tooling questions, the engines reached for repositories and tutorials instead. If you were about to spend this quarter on Reddit, the data says spend it elsewhere — for this category, at least. 4. Where YouTube appears, it is someone else's tutorial All nine YouTube citations are setup tutorials, and eight of them are about one competitor, by name, walking through a configuration the viewer could copy. What we took away from it Publish where the engines already read. For this category that is repositories, issue threads, and long-form tutorial posts — not launch announcements. Your boring pages are answer pages. Pricing, terms, privacy, and sub-processor lists answer real questions that people ask engines. One competitor collected four citations from legal pages in a single question. Expect the long tail. 81% of citations spread across 336 domains. There is no single placement that fixes visibility, which also means no single competitor can lock it up. Limits One engine. One day. 27 questions, all of them ours, chosen to cover what we care about. A different question set or a different date would produce a different distribution. Three of the four engines returned no citations at all because they do not expose them — so this study says nothing about how those three answer, only about which one is measurable. Treat it as a snapshot, not a trend. Disclosure We operate FreeModel, and our product is one of the things these 27 questions ask about. In this round it received zero citations. Every competitor named above was cited more often than we were. We are publishing the method and the distribution rather than a conclusion, because the number that matters is the one you can re-run. The full write-up, with the same numbers, is on our site: https://freemodel.online/compare/ai-citation-study/

来源报道 · 1 篇 · 以下链接均前往原始媒体

← 返回精选动态 原文

更多内容