Embedded UI guidelines

Ready-made UI components will be published after D5. This page will then document the component catalog, theme variables, accessibility requirements, and upgrade guidance. The current page does not promise component names or installation interfaces.

Until then, build UI directly on the self-service API and follow these constraints:

• Use clear customer terms such as balance, reserved, transactions, plans, and billing details.
• Treat server-returned decimal strings as authoritative for money and Credits.
• Distinguish loading, empty, restricted, and temporarily unavailable states.
• Never send access tokens or request and response bodies to logs or analytics.
• Support keyboard access, screen readers, dynamic type, and high contrast.