Everything you need,
nothing you don’t.

Short, practical guides with supported and preview surfaces clearly separated. The fastest way to learn Chirp is to follow the activation rail and watch what happens.

Supported

The implementation and distribution path are verified for the documented release.

Preview

Source may exist, but registry ownership, hosted artifact publication, or the end-to-end release path still needs verification.

Start here

Guides

Don’t see your stack?

Every SDK in the world can speak HTTP. Chirp is four endpoints — /notify, /activity/start, /activity/update, /activity/end. Use a narrowly scoped server credential, keep it in a secret store, and verify both acceptance and device delivery.