Launch HN: Voygr (YC W26) – Voygr：专为代理和 AI 应用打造的更出色的地图 API
13 分•作者: ymarkov•5 天前
大家好，我们是 Yarik 和 Vlad，来自 VOYGR (<a href="https://voygr.tech/">https://voygr.tech/</a>)，致力于为应用开发者和代理商提供更好的真实世界地点智能。这里有一个演示：<a href="https://www.youtube.com/watch?v=cNIpcWIE0n4" rel="nofollow">https://www.youtube.com/watch?v=cNIpcWIE0n4</a>。
谷歌地图可以告诉你一家餐厅是“4.2 星，营业到晚上 10 点”。但他们的 API 无法告诉你厨师上个月已经离职，等待时间翻倍，而且当地人已经不再光顾。如今的地图 API 只能给你一个固定的快照。我们正在构建一个无限的、可查询的地点档案，它将准确的地点数据与新鲜的网络上下文（如新闻、文章和活动）相结合。
Vlad 曾在谷歌地图 API 以及网约车和旅游行业工作。Yarik 曾领导苹果、谷歌和 Meta 的机器学习/搜索基础设施，为每天数亿用户使用的产品提供支持。我们意识到没有人将地点数据的时效性视为基础设施，所以我们正在构建它。
我们从最难的部分开始——确定一个地方是否真实存在。我们的业务验证 API (<a href="https://github.com/voygr-tech/dev-tools" rel="nofollow">https://github.com/voygr-tech/dev-tools</a>) 可以告诉你一个企业是否仍在运营、已经关闭、更名或无效。我们聚合多个数据源，检测冲突信号，并返回一个结构化的判断结果。可以把它想象成针对现实世界的持续集成。
问题在于：大约 40% 的谷歌搜索和高达 20% 的 LLM 提示都涉及本地上下文。每年有 25-30% 的地点会发生变动。世界不会主动发出结构化的“我已关闭”事件——你必须主动检测它。随着代理开始在现实世界中搜索、预订和购物，这个问题会扩大 10 倍——但没有人为此构建基础设施。我们最近对 LLM 处理本地地点查询的能力进行了基准测试 (<a href="https://news.ycombinator.com/item?id=47366423">https://news.ycombinator.com/item?id=47366423</a>)——结果很糟糕：即使是最好的模型，在 12 个本地查询中也会出错 1 次。
我们每天为企业客户（包括领先的地图和科技公司）处理数万个地点。今天，我们向开发者社区开放 API 访问权限。请在此处查找详细信息：<a href="https://github.com/voygr-tech/dev-tools" rel="nofollow">https://github.com/voygr-tech/dev-tools</a>
我们很乐意听取诚实的反馈——无论是关于问题、我们的方法，还是你认为我们哪里错了。如果你在自己的产品中处理过过时的地点数据，我们特别希望听到哪些地方出现了问题。我们今天都在这里，欢迎提问。
查看原文
Hi HN, we’re Yarik and Vlad from VOYGR (<a href="https://voygr.tech/">https://voygr.tech/</a>), working on better real-world place intelligence for app developers and agents. Here’s a demo: <a href="https://www.youtube.com/watch?v=cNIpcWIE0n4" rel="nofollow">https://www.youtube.com/watch?v=cNIpcWIE0n4</a>.<p>Google Maps can tell you a restaurant is "4.2 stars, open till 10." Their API can't tell you the chef left last month, wait times doubled, and locals moved on. Maps APIs today just give you a fixed snapshot. We're building an infinite, queryable place profile that combines accurate place data with fresh web context like news, articles, and events.<p>Vlad worked on the Google Maps APIs as well as in ridesharing and travel. Yarik led ML/Search infrastructure at Apple, Google, and Meta powering products used by hundreds of millions of users daily. We realized nobody was treating place data freshness as infrastructure, so we're building it.<p>We started with one of the hardest parts - knowing whether a place is even real. Our Business Validation API (<a href="https://github.com/voygr-tech/dev-tools" rel="nofollow">https://github.com/voygr-tech/dev-tools</a>) tells you whether a business is actually operating, closed, rebranded, or invalid. We aggregate multiple data sources, detect conflicting signals, and return a structured verdict. Think of it as continuous integration, but for the physical world.<p>The problem: ~40% of Google searches and up to 20% of LLM prompts involve local context. 25-30% of places churn every year. The world doesn't emit structured "I closed" events - you have to actively detect it. As agents start searching, booking, and shopping in the real world, this problem gets 10x bigger - and nobody's building the infrastructure for it. We recently benchmarked how well LLMs handle local place queries (<a href="https://news.ycombinator.com/item?id=47366423">https://news.ycombinator.com/item?id=47366423</a>) - the results were bad: even the best gets 1 in 12 local queries wrong<p>We're processing tens of thousands of places per day for enterprise customers, including leading mapping and tech companies. Today we're opening API access to the developer community. Please find details here: <a href="https://github.com/voygr-tech/dev-tools" rel="nofollow">https://github.com/voygr-tech/dev-tools</a><p>We'd love honest feedback - whether it's about the problem, our approach, or where you think we're wrong. If you're dealing with stale place data in your own products, we'd especially love to hear what breaks. We're here all day, AMA.