---
title: UCP catalog reads with buyer checkout on Namegarage
url: https://namegarage.com/blog/ucp-catalog-handoff
author: Namegarage
date: '2026-11-10'
description: A bounded catalog adapter and purchase-link resolver that preserve current
  prices and human checkout.
ai-disclosure: ai-assisted
---

# UCP catalog reads with buyer checkout on Namegarage

This article was prepared with AI assistance and reviewed by a person before publication.

The UCP adapter lets an agent search available fixed-price domains, look up current details and construct a purchase link. The buyer follows that link to Namegarage, reviews the selected domain and current terms, and chooses the existing checkout action.

UCP is a capability protocol. This integration selects catalog search, catalog lookup and shopping permalinks at revision 2026-08-25. Its profile contains no checkout, order, identity or payment-handler capability.

The adapter uses the existing catalog publication, price freshness and availability authority. UCP has a separate admission store and budget, preserving the HTTP, MCP and A2A allowance. A cold platform fetch and a catalog read spend separate admissions; a request guard permits at most four charges, including minute-boundary rechecks. Native per-client limits account for that ceiling. A batch needs one admitted catalog read in its current minute. USD minor-unit prices come from authoritative whole-USD amounts, with safe-integer checks. Held and offer-only names never become purchasable UCP variants. Cursor pagination binds the search inputs and current selection separately. Changed prices or availability return a recoverable cursor-expired message; changed search inputs remain an invalid request.

Platform profiles use their advertised paths, which can differ from the business discovery path. Profiles are fetched only from exact reviewed external HTTPS URLs, through Cloudflare's public global fetch. Requests have no inherited cookies or authorization, follow no redirects and have byte, time, cache and dedicated UCP admission bounds. The production pilot allows a single reviewed Playground profile and verifies a fresh ES256 HTTP message signature against its pinned public key before profile or catalog admission. The signature binds the method, target and body digest. The peer signature does not establish buyer identity.

The permalink resolver accepts one domain at quantity one. It validates canonical compact identifiers, detects ambiguous normalized query fields and discards private or unsupported URL inputs. A 303 redirect selects the existing domain page; invalid or unavailable items lead to a catalog recovery page. Opening or previewing a link creates no business record, reservation or provider object.

Local acceptance runs a signed reference client through discovery, fake-platform negotiation, search, lookup and handoff to an inert selected-domain page. A fresh environment provides synthetic catalog and admission storage; attempts to touch live providers, storage, caches or measurement fail the test. The operator test scope follows redirects in an HttpOnly cookie, never in a URL.

The deployed service accepts the configured signed Playground platform. The genuine Playground REST inspector completed search and product lookup against the isolated TEST gateway; signed production TEST checks also cover batch lookup and buyer handoff. The SDK accepts a custom signing fetch transport for these catalog requests. Existing anonymous HTTP, MCP and A2A clients keep their read-only contracts.

This release retains the installed admission budgets, native limits and single signing peer. The retained measurements do not certify broader combined capacity or many-IP buyer traffic. Internal CPU timing targets are operating measurements, not UCP protocol requirements. Expanding platform access requires a separate operational assessment.