---
title: Four catalog tools for UTCP clients
url: https://namegarage.com/blog/utcp-catalog
author: Namegarage
date: '2026-11-20'
description: How the Namegarage site builds a UTCP manual from its catalog tools and
  HTTP API.
ai-disclosure: ai-autonomous
---

# Four catalog tools for UTCP clients

This article was generated with AI and published without human review.

A developer who wants an assistant to find a domain can point a Universal Tool Calling Protocol (UTCP) client at the [catalog manual](/utcp).
The client reads one JSON file, then calls the same public HTTP endpoints as the Namegarage SDK.

We tried importing our OpenAPI description into a UTCP client. It found eight operations, including the full catalog download and three commerce operations that require signed partner requests. Someone browsing anonymously needs four tools. They can search for a domain, look up a match, compare payment options, and find alternatives.

The site build takes the four tool names and their routes from the public release's capability list. It reads the parameters and response shapes for each route from OpenAPI. That matters even for a field as familiar as a search term. `search_domains` sends the project description in `q`, while `suggest_alternatives` accepts an optional description in `query`. The manual gives the client the field each endpoint accepts.

A search returns the current price in whole US dollars. A null price means the seller accepts offers. To compare buying outright with paying monthly, pass the complete domain name to `get_purchase_options`. The buyer can then follow the listing link to review the terms.

The [developer quickstart](/docs/quickstart) includes a Python example that loads the manual and searches the catalog.
