One public catalog contract for HTTP, MCP, SDKs and skills

Dev blog#api#mcp#sdk#skills#releases

A useful assistant integration needs the same facts whichever interface it uses. The catalog release coordinates the HTTP API, MCP tools, JavaScript and TypeScript SDK, and catalog skill. The developer changelog records the exact versions and compatibility notes separately from this engineering blog.

The HTTP API adds three read-only routes:

  • GET /api/domain?name=example.invalid looks up one complete published name, including its published description and potential uses.
  • GET /api/purchase-options?name=example.invalid compares the current outright price with the published standard zero-down lease-to-own schedules.
  • GET /api/alternatives?name=example.invalid&query=project&limit=5 finds other published names and excludes the reference before applying the result limit.

The examples use a fictional .invalid name. A missing listing does not establish registration availability. A null price means offer-only. Search text is sent to Namegarage; keep confidential project details out of it.

SDK 0.2.0 adds getDomain(), getPurchaseOptions() and suggestAlternatives(). All payment amounts come from the server. Compare the monthly payment, final payment, total and extra cost against buying outright; a cash-only discount may not apply to the lease principal. Follow the returned page for current terms, other payment choices and additional checkout fees.

These interfaces share the same publication checks and request allowance. They do not reserve names, create quotes, start checkout, send messages or access private portfolio records. The API reference, SDK quickstart and MCP guide describe the contracts.

Catalog skill 1.1.0 includes the same operations and is available on ClawHub and through the skills.sh install command. Fresh skills.sh installs deliver the new skill; its listing page still shows cached older guidance while the directory refreshes.

Future public changes require a compatibility record across the service, SDK and skill repositories, a developer changelog entry and a dev-blog update. A release remains pending until every affected package and directory is verified.

Comments

Comments are reviewed before publication. The Author badge marks replies from the author.

Read approved comments on the discussion page.

    Open the discussion page

    Leave a comment

    Your account name, sign-in provider, and comment become public after review. Your email stays private. See the blog comments privacy notice and Privacy Policy.

    Sign in to leave a comment.