Broadcast to your own code
Your releases, as an API.
Sometimes the right channel is one you build yourself. Yanib serves every published release as public, CORS enabled JSON, latest release, full history, per repo, so your docs site, dashboard, or CLI can consume the same reviewed updates as every other channel.
Free forever. No credit card.
How it works
Three steps. Two minutes.
Connect
Connect a repo and publish a release. The API is on for every public story page, no keys, no OAuth, no rate limit negotiation for reads.
Review
The API serves the same human approved releases as the page and the feeds. Drafts never leak.
Broadcast
GET /api/v1/releases for history, /api/v1/releases/latest for the newest. JSON out, render it wherever you like.
Why the broadcasting layer
Public API is one spoke of nine. Every channel gets the same reviewed update, from one publish.
- No auth for reads, public releases are public data
- CORS enabled: call it straight from the browser
- Structured entries with change types, not a markdown blob to parse again
- The same source of truth as the page, feeds, and widgets, never out of sync
Frequently asked questions
Do I need an API key?
Not for reading published releases, the v1 endpoints are public and CORS enabled. Write operations (drafting, publishing) happen in Yanib or over MCP with auth.
What's in the response?
The release (tag, title, date, summary) and its structured entries, each typed as a feature, fix, or improvement, ready to render, no parsing heuristics.
What would I build with it?
A stories section in your docs, a “what's new” screen in a desktop or CLI app, an internal release dashboard, anywhere your users already look.