Widgets

Drop-in components for status boards, deadlines, paydays, holidays, and calendars. One script, standard web components, no dependencies. Pick one from the shelf, tune it in the viewer, take the code in your framework.

The viewer

Live against real data. Snippets track every change you make; the key slot fills itself once you mint one below.

<script src="https://chronosapi.dev/embed.js" defer></script>

<chronos-status api-key="pk_your_publishable_key" regions="US,GB,JP,SA"></chronos-status>

Get a publishable key

Widgets run on a publishable key (pk_...): safe in client code, locked to the origins you list, read-only, metered against your normal quota. Your secret key mints it and stays server-side. Signed in? Your account page does this too.

No key yet? Signup takes thirty seconds. Rotating your secret key revokes its publishable keys with it.

Try one without a key

The sample widget is fixed (US, next holiday) and needs nothing:

<script src="https://chronosapi.dev/embed.js" defer></script>
<chronos-demo></chronos-demo>

Options every widget shares

AttributeNotes
api-keyyour publishable key; required everywhere except <chronos-demo>
regionany code from /v1/regions: countries, subdivisions, markets
themewidgets follow the page's color scheme; light or dark pins it
variantdesigned styles: minimal (default), modern, soft, terminal
CSS hooks--chronos-ink, --chronos-muted, --chronos-hair, --chronos-red, --chronos-shade restyle from your stylesheet

Widgets read display endpoints only, store nothing, and carry a small attribution link. For anything beyond display, call the API directly.