The Agent
Intent Protocol

A lightweight, open standard that gives any web application a machine-readable intent layer. AIP is to agents what sitemaps are to search engines.

01

The Integration Gap

No Intent Surface

Agents are forced to scrape HTML and guess UI states. A simple action becomes a fragile sequence of simulated clicks.

Discovery Void

APIs exist, but there is no standard way for an agent to discover what they do or how to authenticate without custom engineering.

Trust Deficit

Agents have no way to verify if an endpoint is legitimate or safe, making every integration a leap of faith.

02

How Jin Works

1. Automated Discovery

The @papercargo/jin-cli scans your codebase, detecting Next.js, Express, and OpenAPI specs to extract your app's intent surface.

$ npx jin init
✓ Found 12 routes
✓ Generated jin.json
{
  "aip_version": "0.1",
  "app": { "name": "Spotter" },
  "intents": [
    {
      "id": "book_trainer",
      "method": "POST",
      "endpoint": "/api/v1/bookings"
    }
  ]
}

2. The Intent Map

Your app serves a jin.json at /.well-known/jin.json. This is the source of truth for any agent.

  • Natural language triggers for matching
  • Strict parameter schemas
  • Safety flags (destructive/confirmation)
"intents": [
  {
    "id": "cancel_booking",
    "triggers": ["cancel my session"],
    "destructive": true,
    "confirmation_required": true
  }
]
03

Collaborate

Build the Legible Web

Jin is an open-source project and a public-domain protocol. Help us build the infrastructure for the agentic era.

GitHub RepositoryGet Started