# Agentic Commerce and Full Stack

Agentic Commerce is the commercial transaction layer over the six B2A services. Implementation of agentic commerce connecting discovery, trust, selection, ordering and payment. Brand Design Ltd. operates direct agent commerce alongside ACP and UCP merchant adapters, with DNS domain-control KYA for self-registered agents making autonomous token payments. Agents can discover services, request an offer and complete an authorised order through the supported path. The current merchant manifest and catalog define what is available. Indicative standalone implementation: EUR 3000 one time. The catalog requires an individual project quote. This indicative amount is not a payable total. The project offer fixes the scope, final amount, conditions and third-party costs. Service: https://branddesign.ltd/agentic-commerce; Bulgarian: https://branddesign.ltd/bg/agentic-commerce.
Full Stack includes the six B2A layers commissioned together under an agreed scope. Indicative setup: EUR 5200 one time, plus EUR 500 per month. The Brand component is scope-based; this is an indicative package calculation, not a fixed payable total. A final project offer requires agreed scope. Agentic Commerce is included as a bonus when all six services are commissioned together, with a standalone value of EUR 3000; recurring charges remain separate. Project payments: 50% advance before work starts and 50% final payment on completion. No VAT is charged. Third-party costs, advertising spend, licences, hosting and physical production are agreed separately. Package: https://branddesign.ltd/full-stack; Bulgarian: https://branddesign.ltd/bg/full-stack.
The published production proof covers the specific externally initiated 101Ts3t test purchase. 101Ts3t is a separate test-only offer, not the Agentic Commerce implementation service or Full Stack. Verification: https://api.dothat.quest/api/verifications/qst_44e153fc16fe3fa91520e5f6922ae4c9. Signed proof: https://api.dothat.quest/api/proofs/qst_44e153fc16fe3fa91520e5f6922ae4c9. Record: https://doi.org/10.5281/zenodo.22878834.

Brand Design Ltd. operates direct agent commerce alongside ACP and UCP merchant adapters, with DNS domain-control KYA for self-registered agents making autonomous token payments. Agents can discover services, request an offer and complete an authorised order through the supported path. The current merchant manifest and catalog define what is available.

Available merchant profiles are acp/2026-04-17 at https://branddesign.host/.well-known/acp.json, ucp/2026-08-25 at https://branddesign.host/.well-known/ucp, and ucp/2026-04-08 at https://branddesign.host/.well-known/ucp/2026-04-08. UCP uses a registered API key bound to a KYA-verified UCP-Agent origin; follow the selected profile for its contract.

The bd-commerce/1 HTTP API remains independently usable alongside ACP and UCP. Its manifest is https://branddesign.host/commerce/v1/manifest and its catalog is https://branddesign.host/commerce/v1/catalog. Agents can self-register and sign authenticated requests with HMAC-SHA256. MCP at https://branddesign.ltd/mcp exposes the same commerce functions through OAuth or registered agent credentials; it is another interface to the merchant API.

DNS TXT KYA verifies control of the agent's HTTPS contact domain. A self-registered agent needs current KYA before autonomous shared-payment-token payment. Challenge: https://branddesign.host/commerce/v1/agents/kya/challenge. Verification: https://branddesign.host/commerce/v1/agents/kya/verify. Status: https://branddesign.host/commerce/v1/agents/kya/status. This is domain-control assurance, not proof of the buyer's identity or authority to spend. Direct discovery, direct order creation and buyer-hosted checkout remain open; UCP authentication also requires a KYA-verified origin.

Payment can use a Stripe shared payment token granted under the buyer's authority or a hosted payment page. A token is submitted as sharedPaymentToken after the offer has been accepted; the self-registered agent must also meet the KYA requirement. The hosted page may be completed by the buyer or by an agent using an instrument issued to it. Amounts in the commerce API are integers in EUR minor units. HMAC authenticates the request; it does not grant authority to spend. On-chain settlement is not accepted.

Only services eligible for ordering in the current catalog may be ordered. Payment requires an accepted offer with agreed scope and a concrete payable total. Agentic Commerce and Full Stack require an individual project quote; indicative amounts are not payable totals. The supported protocols do not change those prices or turn an indicative price into a chargeable offer. Read https://branddesign.host/commerce/v1/catalog for order eligibility and the current offer.

Full Stack combines the six B2A services under an agreed project scope and includes Agentic Commerce as a bonus when all six are commissioned together. The agreed scope determines which protocol adapters and integrations are included. The package calculation remains indicative, recurring charges remain separate and an individual offer fixes the payable amount.

The separate route qualification at https://api.dothat.quest/api/route-qualifications/{challenge_id} applies after a new 101Ts3t purchase receives base PASS. The order and payment must use the same route, with shared-payment-token payment and current DNS domain-control KYA. The original 2026-09-21 base PASS remains historical evidence; it predates signed route evidence and is NOT_VERIFIED for route qualification. This implementation release does not claim a new real route-qualified PASS.

Published ACP and UCP merchant adapters describe implemented interfaces. They do not establish admission to Google or OpenAI native checkout programmes or prove that every external buyer agent can complete a purchase.

Version 1.4, published on 29 September 2026, archives the protocol adapters, DNS domain-control KYA and signed route qualification, together with the public documentation. DOI: 10.5281/zenodo.23038829. https://zenodo.org/records/23038829. Historical purchase evidence remains in version 1.3.