Show HN：Jin - 一种机器可读协议，使互联网对 AI 更加易读
1 分•作者: ankushvishnu•28 天前
大家好！
我正在构建 Jin，这是一个面向 AI 代理构建者和网站管理员的开源协议，旨在让日常互联网对 AI 代理来说更易于理解。
我使用 AI 代理进行编码和研究，我观察到一个现象是，我们在赋予代理抓取能力上花费了过多的时间、金钱或两者兼有。这让我思考，如果有一种系统，能让我的 AI 代理在不费吹灰之力的情况下，就能获取我想要的互联网信息，那该多好？由此我产生了“意图层”的想法。
Jin 的工作原理如下：
1. **AI 代理端：** 您只需以 `skill.json` 或 `skill.xml` 的格式将指令传递给您的代理。这是第一步。该技能会指示代理在网站上查找 `jin.json`，并使用意图映射进行导航，执行 CRUD 等操作。它位于 `app/.well-known/jin.json` 下。
2. **网站管理员端：** 网站管理员可以在其项目根目录下运行 `jin-cli`。该 CLI 会映射项目，生成一个 `jin.json` 文件中的意图映射，并将其保存在应用程序所在的位置。例如，在单体结构中，`jin.json` 可以放在根目录下。对于单体仓库结构，它可以放在 `app/web` 或 `app/marketing` 等目录下。这个文件可以完全按照您的意愿进行编辑。除了生成意图映射，它还会告诉您如何轻松进行编辑，可以包含什么内容，什么应该包含，什么不应该包含等等。`jin.json` 中有一个待办事项列表。
此外，在最新版本中，我添加了一个 Jin Shield 来保护网站免受未经授权的抓取。这个 Shield 与您正在使用的任何防火墙并存，可以将其视为第一道防线。它会记录谁访问了网站。您可以在 meetjin.com 上免费注册您的代理，并使用生成的密钥访问任何使用 Jin Shield 的网站。代理会携带一个加密的 RS256 JWT 凭证，Jin Shield 会使用缓存的 JWKS 公钥在本地验证此凭证。
规范是开放的（CC0），工具是 Apache 2.0 许可。请随意使用、修改、批评或赞扬它。
访问 CLI：`npx @papercargo/jin-cli`
获取密钥：<https://meetjin.com>
GitHub：<https://github.com/meetjin/jin>
我非常希望能了解您的用例和反馈。
祝好！
查看原文
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!