<?xml version="1.0" encoding="UTF-8"?>
<reference anchor="I-D.hood-independent-agtp" target="https://datatracker.ietf.org/doc/html/draft-hood-independent-agtp-00">
   <front>
      <title>Agent Transfer Protocol (AGTP)</title>
      <author initials="C." surname="Hood" fullname="Chris Hood">
         <organization>Nomotic, Inc.</organization>
      </author>
      <date month="March" day="19" year="2026" />
      <abstract>
	 <t>   AI agents and agentic systems generate a growing volume of intent-
   driven, unstructured, and undifferentiated traffic that flows through
   HTTP indistinguishably from human-initiated requests.  HTTP lacks the
   semantic vocabulary, observability primitives, and identity
   mechanisms required by agent systems operating at scale.  Existing
   protocols described as &quot;agent protocols&quot; including MCP, ACP, A2A, and
   ANP, are messaging-layer constructs that presuppose HTTP as their
   transport.  They do not address the underlying transport problem.

   This document defines the Agent Transfer Protocol (AGTP): a dedicated
   application-layer protocol for AI agent traffic.  AGTP provides
   agent-native intent methods (QUERY, SUMMARIZE, BOOK, SCHEDULE, LEARN,
   DELEGATE, COLLABORATE, CONFIRM, ESCALATE, NOTIFY), protocol-level
   agent identity and authority headers, and a status code vocabulary
   designed for the conditions AI agent systems encounter.  AGTP SHOULD
   prefer QUIC for new implementations and MUST support TCP/TLS for
   compatibility and fallback.  It is designed to be composable with
   existing agent frameworks, not to replace them.

	 </t>
      </abstract>
   </front>
   <seriesInfo name="Internet-Draft" value="draft-hood-independent-agtp-00" />
   
</reference>
