<?xml version="1.0" encoding="UTF-8"?>
<reference anchor="I-D.hood-agtp-api" target="https://datatracker.ietf.org/doc/html/draft-hood-agtp-api-01">
   <front>
      <title>AGTP-API: Verbs, Paths, Endpoints, and Synthesis</title>
      <author initials="C." surname="Hood" fullname="Chris Hood">
         <organization>Nomotic, Inc.</organization>
      </author>
      <date month="May" day="25" year="2026" />
      <abstract>
	 <t>   This document specifies AGTP-API: the contract layer that the Agent
   Transfer Protocol (AGTP) [AGTP] relies on to govern interactions
   between autonomous agents and AGTP servers.  AGTP-API defines a
   curated approved method catalog (with versioned evolution and
   graceful deprecation), path grammar rules that prevent method-name
   leakage into paths, the endpoint primitive (the structural unit a
   server exposes to agents), the semantic block carried by every
   endpoint, schema validation requirements, the server manifest format
   that exposes a server&#x27;s endpoint catalog, the per-server method
   policy carried as a sub-block of the manifest, the PROPOSE-and-
   synthesis runtime contract negotiation mechanism, the three handler
   binding kinds (composition, registered_function, external_service),
   and the structural rejection status codes (404, 405, 459, 460) that
   together cover the contract-level failure surface.  This document
   supersedes the AGIS Internet-Draft (draft-hood-independent-agis-01)
   and the previously-proposed AGTP-Methods Internet-Draft, both of
   which are deprecated.  AGTP-API is the unified companion
   specification they were splitting concerns across.

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