Dev weekly: one catalog across APIs, assistants, and the website

A domain shortlist is useful only if the next tool can read the same listing and payment facts. This week's engineering work connected the public catalog across HTTP, MCP, JavaScript and TypeScript, and agent skills.

This roundup covers October 25–31, 2026. It summarizes published engineering articles; the Developers changelog retains the exact versions and publication status.

Carry the facts across interfaces

The coordinated catalog update exposes three related operations: look up one published name, compare its purchase options, and find alternatives from the catalog. The SDK methods are getDomain(), getPurchaseOptions(), and suggestAlternatives().

The payment comparison returns server-calculated amounts. A client should compare the regular monthly amount, final payment, total cost, and extra cost against an outright purchase. A cash-only weekly discount may leave the lease principal unchanged. A null price means offer-only; a missing listing does not establish registration availability.

These interfaces share the public read boundary. They cannot reserve a domain, start checkout, send a message, or read private portfolio records. A result links back to the domain page for current terms and purchase choices.

Make the entry points easy to find

The API quickstart and official SDK introduction give developers examples without an account or API key. The SDK includes TypeScript declarations, ESM and CommonJS support, cancellation, timeouts, and typed errors. It does not retry automatically; callers must honor Retry-After.

Discovery metadata points agents to OpenAPI and MCP. Compatibility URLs describe the same public interfaces, and the official npm aliases forward to the scoped SDK. The Poppy entry point adds another route for personal agents to discover those public resources.

The website's assistant setup page lets readers select an assistant and copy its connection details or example prompts. Markdown access gives agents a readable homepage and blog articles alongside the catalog interfaces.

Declare where AI wrote the text

The AI disclosure article explains our element-level authorship labels. A page can contain AI-written descriptions, catalog prices, reader comments, and purchase controls. A declaration on one passage should describe that passage.

The attributes come from a community proposal, not an established HTML standard. A matching Markdown field and visible notice preserve the declaration when a collector reads an article as text. The labels describe authorship; they do not certify accuracy or enforce exclusion from training.

Human review also has a specific meaning. An AI checking another AI's output does not establish that a person read it. The distinction matters when the site labels a passage as AI-assisted.

Keep publication status visible

The current coordinated release record is still marked upcoming, with external directory acceptance outstanding. Published catalog operations and available packages can be described on their own evidence; the entire release cannot be called complete.

For the buyer-facing effect of this work and the dated deal selection, read the companion consumer roundup.