<?xml version="1.0" encoding="UTF-8"?>
<reference anchor="I-D.hood-agtp-merchant-identity" target="https://datatracker.ietf.org/doc/html/draft-hood-agtp-merchant-identity-00">
   <front>
      <title>AGTP Merchant Identity and Agentic Commerce Binding</title>
      <author initials="C." surname="Hood" fullname="Chris Hood">
         <organization>Nomotic, Inc.</organization>
      </author>
      <date month="April" day="17" year="2026" />
      <abstract>
	 <t>   The Agent Transfer Protocol (AGTP) specifies the sending side of an
   agentic transaction: agent identity, Authority-Scope enforcement,
   Budget- Limit declaration, and a signed Attribution-Record on every
   method invocation.  The receiving side of a PURCHASE transaction --
   the merchant or service provider -- has no equivalent protocol-level
   identity or verification mechanism.  This is the merchant identity
   gap.

   This document specifies the AGTP Merchant Identity and Agentic
   Commerce Binding.  It defines the Merchant Manifest Document, a
   signed identity record structurally parallel to the Agent Manifest
   Document; the Merchant Birth Certificate, the genesis record from
   which a merchant&#x27;s canonical identifier is derived; Merchant Trust
   Tiers aligned with AGTP Trust Tier semantics; and the protocol
   integration points at which merchant identity is verified.  These
   include the PURCHASE method handshake, the DISCOVER method result
   surface, and the Attribution-Record.  This document also defines the
   Intent-Assertion header for portable, detached principal- authorized
   intent, the Cart-Digest mechanism for multi-line-item transactions,
   and the 455 Counterparty Unverified status code.  Together these
   mechanisms close the verification loop between agent and merchant
   within AGTP&#x27;s governance model.

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