@techreport{hood-agtp-api-01,
    number =    {draft-hood-agtp-api-01},
    type =      {Internet-Draft},
    institution =   {Internet Engineering Task Force},
    publisher = {Internet Engineering Task Force},
    note =      {Work in Progress},
    url =       {https://datatracker.ietf.org/doc/draft-hood-agtp-api/01/},
    author =    {Chris Hood},
    title =     {{AGTP-API: Verbs, Paths, Endpoints, and Synthesis}},
    pagetotal = 82,
    year =      2026,
    month =     may,
    day =       25,
    abstract =  {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'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.},
}