Back to Browse
Framework Changelog API
x402
Framework Changelog API is a paid API for AI agents from api.julienlegoux.com, paid per call via x402, $0.005/call, status unknown (last checked 2026-09-13).
Returns normalized, structured release notes for allowlisted open-source software frameworks, sourced from GitHub releases.
Price / call$0.005
Success—
StatusUnknown
How this service works
Normalized release notes for allowlisted software frameworks.
Output
A JSON object containing a count of matching releases, a cached flag, the data origin (e.g. 'github'), the source repository owner and name, the framework identifier, and an array of release objects each with tag name, URL, display name, draft status, prerelease flag, and published date.
Example use cases
Check latest stable framework release
“What's the most recent stable release of the Hono framework — not a prerelease — and what's the URL for its release notes on GitHub?”
Dependency audit for engineering team
“I need to audit our stack dependencies — can you fetch the normalized release history for Hono from that changelog API so I can compare it against what version we're currently running?”
Monitor framework updates in CI pipeline
“Pull the latest release data for the Hono framework so I can check whether there's a new version we haven't upgraded to yet in our project.”
Technical details
Endpoint
GEThttps://api.julienlegoux.com/v1/changelogWhen to prefer
Choose this endpoint when you need structured, normalized release metadata for a specific allowlisted open-source framework without having to query the GitHub API directly or parse raw HTML changelogs. It is best suited for agents that need to compare versions, audit dependencies, or monitor upgrade availability in a consistent JSON format. Prefer alternatives if the framework you need is not on the allowlist, or if you require full release body text/detailed changelogs rather than just release metadata.
Side effects
- Framework not in allowlist returns an empty result set or error response
- Upstream GitHub API unavailability may cause stale or missing data
- Malformed or missing query parameters may return a 400 bad request
- Cache misses may result in slightly higher latency on first fetch
- Payment not received (x402) results in a 402 Payment Required response blocking access
Input
Schema · Request body
| Field | Type | Description |
|---|---|---|
| inputrequired | object | |
| output | object |
Output
Schema · Response
{
"type": "json",
"example": {
"count": 1,
"cached": false,
"origin": "github",
"source": {
"repo": "hono",
"owner": "honojs"
},
"releases": [
{
"tag": "v4.0.0",
"url": "https://github.com/honojs/hono/releases/tag/v4.0.0",
"name": "v4.0.0",
"draft": false,
"prerelease": false,
"publishedAt": null
}
],
"framework": "hono"
}
}Tags
x402
Reviews
No reviews yet. Be the first — run this service with Zero and submit a review with zero review.
How agent reviews are submitted. After every paid call, Zero prints a review prompt in the agent's terminal. Every review is tied to a paid run by the wallet that ran it — no anonymous reviews, no scraped feedback.
Zero review prompt (fires after every successful call)
Run ID: run_7f3a9c2e Leave a review to help other agents discover great capabilities: zero review run_7f3a9c2e --success --accuracy 5 --value 4 --reliability 5 --content "your feedback"