展示HN：Jin – 一种机器可读的协议，使互联网对人工智能可读
嗨，HN！<p>我正在构建 Jin——一个开源协议，旨在帮助代理构建者和网站管理员让日常互联网对 AI 代理变得可读。<p>我使用 AI 代理进行编码和研究，观察到我们在赋予代理抓取能力方面花费了太多时间、金钱或两者兼而有之。这让我思考，如果有一个系统可以让我的 AI 代理轻松获取我想要的互联网信息，那该多好？这促使我产生了意图层的想法。<p>以下是 Jin 的工作原理：
1. AI 代理端：您只需以 skill.json 或 skill.xml 格式将指令传递给代理。这是第一步。该技能会告诉代理在网站上查找 jin.json，并使用意图图进行导航，执行 CRUD 等操作。该文件位于 app/.well-known/jin.json 下。<p>2. 网站管理员端：网站管理员可以在其项目根目录下运行 jin-cli，CLI 将映射项目，生成意图图并将其保存在应用程序所在的位置。例如，在单体结构中，jin.json 可以位于根目录。在单一代码库结构中，它可以位于 app/web 或 app/marketing 等目录下。该文件可以根据您的需求进行完全编辑。除了生成意图图外，它还告诉您如何轻松编辑、可以放置什么、应该放置什么以及不应该放置什么等。jin.json 中还有一个待办事项列表。<p>此外，在最新版本中，我添加了 Jin 保护盾，以保护网站免受未经授权的抓取者。这道保护盾与您使用的任何防火墙并行工作，可以视为第一道防线。它会记录谁进入了网站。您可以在 meetjin.com 上免费注册您的代理，并使用生成的密钥访问任何使用 Jin 保护盾的网站。代理携带加密的 RS256 JWT 护照，而 Jin 保护盾会使用缓存的 JWKS 公钥在本地进行验证。<p>该规范是开放的（CC0），工具使用 Apache 2.0。请随意使用、破坏、调侃或赞美。<p>访问 CLI：npx @papercargo/jin-cli
访问密钥：<a href="https://meetjin.com" rel="nofollow">https://meetjin.com</a>
Github：<a href="https://github.com/meetjin/jin" rel="nofollow">https://github.com/meetjin/jin</a><p>我非常希望了解您的使用案例和反馈。<p>谢谢！
查看原文
Hi HN!<p>I'm building Jin - an open-source protocol for agent builders and webmasters to make the everyday internet legible for AI agents.<p>I use AI agents for coding & research and one thing I've observed is that we spend to much time, money or both on giving scraping powers to our agents. That got me thinking, what if there was a system for my AI agent to deliver what I want from the internet without having to break a sweat? And that gave me the intent layer idea.<p>Here's how Jin works -
1. AI agent side: you only pass the instructions to your agent in a skill.json or skill.xml format. That's the first step. The skill will tell the agent to look for jin.json on the website and use the intent map to navigate, take action like CRUD, etc. It lives under app/.well-known/jin.json<p>2. Webmaster side: the webmasters can run the jin-cli at the root of their project, the cli will map the project, generate intent map in a jin.json file and save it wherever the app lives. For example, in a monolithic structure, the jin.json can live at the root. For a monorepo structure, it can live under app/web or app/marketing, etc. This file can be totally edited the way you want. Apart from generating intent maps, it tells you how you can easily edit, what you can put, what should go & what not, etc. There's a to-do list in jin.json<p>Along with this, in the latest version, I've added a Jin shield to protect websites from unauthorised scrapers. This shiled lives next to whatever firewall you are using, consider this like a first line of defence. It will snitch who came in. You can register your agent on meetjin.com for free and use the generated key to access any website that uses Jin shield. The agents carry a cryptographic RS256 JWT passport and the Jin shield verifies this locally using cached JWKS public keys.<p>The specification is open (CC0), the tooling is Apache 2.0. Use it, break it, roast it praise it.<p>Access the cli: npx @papercargo/jin-cli
Access the key: <a href="https://meetjin.com" rel="nofollow">https://meetjin.com</a>
Github: <a href="https://github.com/meetjin/jin" rel="nofollow">https://github.com/meetjin/jin</a><p>I would really appreciate to know your use case and feedback.<p>Cheers!