{
 "acronym": "AITP",
 "adoption": {
  "by": "NEAR AI (agents built on the NEAR AI Hub are claimed to 'support all AITP features')",
  "level": "claimed",
  "probe_run": null
 },
 "aliases": [
  "Agent Interaction & Transaction Protocol"
 ],
 "analog": "HTTP+HTML for agent-to-agent interaction, per the project's own framing",
 "collisions": [],
 "discovery": {
  "mechanism": "None defined by AITP itself; agents are addressed directly once discovered out of band (e.g. via the NEAR AI Hub's own agent registry, which is outside the AITP spec)",
  "path": null
 },
 "dispute": null,
 "evidence": [
  {
   "claim": "AITP's homepage states Version: 0.1.0, Status: Draft, and describes the protocol as two parts — a core Threads protocol (inspired by and largely compatible with the OpenAI Assistant/Threads API) and an extensible Capabilities layer for structured interactions like multimodal input, generative UI, payments, and human-in-the-loop attestations.",
   "date": "2026-09-06",
   "label": "VERIFIED",
   "url": "https://aitp.dev/"
  },
  {
   "claim": "The nearai/aitp GitHub repository (MIT license, 25 stars, 4 forks) confirms the same version/status and hosts the capability schemas directory; its README frames AITP as complementary to (not a replacement for) multi-agent orchestration frameworks, service-metadata protocols like MCP, and browser-use agents.",
   "date": "2026-09-06",
   "label": "VERIFIED",
   "url": "https://github.com/nearai/aitp"
  }
 ],
 "form": "endpoint",
 "governance": "NEAR AI-led open-source specification, MIT licensed (github.com/nearai/aitp); developed in parallel with NEAR AI's own agent hub and community input via Telegram/GitHub issues and PRs; no independent standards body",
 "group": null,
 "history": [
  {
   "date": "2026-09-06",
   "note": "added from arXiv 2504.16736 survey comparison, verified against aitp.dev, github.com/nearai/aitp"
  }
 ],
 "id": "aitp",
 "implementation": "prototype",
 "last_verified": "2026-09-06",
 "name": "AITP (Agent Interaction & Transaction Protocol)",
 "native_status": "Version: 0.1.0. Status: Draft. \"AITP is a spec in progress and we are open to comments, feedback, and contributions\" (project's own words)",
 "origin": {
  "date": "2025",
  "org": "NEAR AI (NEAR Foundation)"
 },
 "part_of": null,
 "parties": [
  "agent-agent",
  "agent-human"
 ],
 "phase": "draft",
 "probe": {
  "method": "POST",
  "on_absent": "A 404 or a Threads-API-shaped response with no Capability exchange means this origin either doesn't speak AITP or only speaks the underlying OpenAI-compatible Threads transport without AITP's capability layer.",
  "parse": "A response containing a Thread object 'largely compatible with the OpenAI Assistant/Threads API' is necessary but not sufficient; confirming AITP specifically requires observing a Capability-exchange message (per the capabilities schema) rather than plain-text-only thread content.",
  "path": "{origin}/threads"
 },
 "question": "How do two agents representing different, mutually untrusted people or businesses (e.g. a personal assistant and an airline's booking agent) talk to each other, exchange forms and payment requests, and not just plain text?",
 "scope": "general",
 "spec_url": "https://aitp.dev/",
 "step": "coordinate",
 "summary_md": "AITP (Agent Interaction & Transaction Protocol), published by NEAR AI, is a draft specification for AI agents to communicate securely across trust boundaries — the project's canonical example is a personal AI assistant booking a flight by talking directly to an airline's own booking agent, exchanging structured flight options, passenger details, and payment information over a shared protocol rather than the assistant scraping the airline's website [1]. It consists of two parts: a core Threads protocol for the conversation itself, described as 'inspired by and largely compatible with' OpenAI's Assistant/Threads API, and an extensible Capabilities layer — standardized message types agents can negotiate to support structured interactions such as multimodal input, generative UI (forms, buttons), payment requests, and human-in-the-loop attestations [1][2].\n\nAITP explicitly positions itself as complementary to, not competing with, three adjacent categories: same-owner multi-agent orchestration frameworks (CrewAI, Autogen, LangGraph), service-metadata protocols that let agents call existing APIs (MCP, Bitte, llms.txt), and browser-use agents that navigate existing websites (ChatGPT Operator) — the project frames the last of these as merely 'transitional, useful until AITP adoption grows' [2]. It does not define its own transport-layer security scheme beyond what a chosen Transport (e.g. HTTPS) provides, and does not define agent discovery: personal assistants and service agents are expected to already know how to reach each other, typically via the NEAR AI Hub's own agent registry, which sits outside the AITP spec itself [1].\n\nAs of this check (September 2026), AITP remains at version 0.1.0 and Draft status; the project states plainly that the spec is being written simultaneously with its own reference implementation (NEAR AI Hub agents) and is actively soliciting feedback before a 1.0 release [1][2]. The only implementations identified are NEAR AI's own — agents built on app.near.ai/agents are claimed by NEAR AI to support all AITP features — with no independent, non-NEAR production adopter confirmed during this verification pass, so adoption here is recorded as claimed rather than measured. What remains unresolved: how AITP's Capabilities layer (particularly payments, which relies on unspecified external settlement rails) will interoperate with the payment-specific protocols already on this map, and whether any framework or platform outside the NEAR ecosystem has committed to implementing AITP ahead of a stable 1.0.",
 "track": "single-vendor",
 "version": {
  "date": null,
  "label": "0.1.0 (Draft)"
 },
 "url": "https://agenticweb.wiki/protocols/aitp/",
 "category": "coordinate",
 "type": "protocol"
}