Gummy UI
EN

Published language

Englishen

19 more locales are awaiting founder review and publication.

Translation status

AI and agent discovery

A catalogue agents can inspect safely.

Public metadata exposes names, semantics, keyboard contracts, dependencies, docs, and registry URLs without exposing any paid source.

Discovery endpoints

Catalogue JSON

All 57 definitions from the same manifest that builds the website.

/api/catalogue

LLM index

Concise agent-readable descriptions and canonical links.

/llms.txt

Registry payload

Editable source plus explicit package and registry dependencies.

/r/gummy-button.json

Health

Public service and catalogue-count signal without private diagnostics.

/api/health

Agent installation policy

  1. Read the component detail and behavior contract.
  2. Install through the canonical registry URL.
  3. Keep the copied source editable in the consuming repository.
  4. Preserve native, Base UI, or Radix UI semantics while changing visual tokens.
  5. Never infer or request paid source from public preview metadata.

MCP transport status

The public HTTP catalogue and registry contracts are implemented. A hosted MCP transport remains a release gate: it will not be advertised as live until authentication, rate limits, monitoring, and production deployment are approved.

Safe automated consumption

An agent should treat catalogue metadata as a discovery aid and the registry response as code proposed for the consuming repository. Before writing files, it should identify the requested component, show the destination paths, resolve declared dependencies, and allow existing local changes to take priority. After installation, normal formatting, type, interaction, accessibility, and production-build checks still apply; a successful HTTP response is not verification of the resulting product.

Registry source is public and MIT licensed, but prompts, logs, build output, or provider calls must not be used to reconstruct private Pro assets. Public Pro metadata can answer whether an item is specified, implemented, verified, or release-ready. It cannot grant an entitlement or name a private path, archive, test, or source file.

Reliability and versioning

Consumers should pin reviewed source in their own version control rather than depending on this site at application runtime. If a future hosted transport is released, its authentication and rate limits will protect service availability, not change the licence or make agent output trustworthy by default. Health responses remain intentionally narrow so monitoring can detect service state without exposing credentials, customer records, or private diagnostics.