Back to Browse
docs-changelog
x402
docs-changelog is a paid API for AI agents from payai.agentstools.dev, paid per call via x402, $0.008/call, status unknown (last checked 2026-10-12).
Returns GitHub release notes, intermediate registry versions, and breaking-change markers for a library upgrade range across npm, PyPI, crates.io, or GitHub repos.
Price / call$0.008
Success—
StatusUnknown
How this service works
Version-delta changelog for a library between two versions. Give an ecosystem, package name and from_version and to_version and get the GitHub release notes in that range, the registry versions between them, and surfaced breaking-change markers. Built for agents deciding whether an upgrade is safe.
Output
An object containing GitHub release notes for each version in the specified range, a list of intermediate registry versions between from_version and to_version, and surfaced breaking-change markers (e.g. semver major bumps, explicit BREAKING CHANGE annotations in release notes) to help an agent assess upgrade safety.
Example use cases
Pre-upgrade safety check for npm package
“Before I upgrade axios from 0.27.0 to 1.6.0 in my Node project, can you pull the changelog and flag any breaking changes I need to worry about?”
Rust crate upgrade audit
“I'm bumping tokio from 1.28.0 to 1.36.0 in my Rust project — what did the crates.io releases cover in that range and were there any breaking API changes?”
Python library version delta review
“What changed in the pypi package 'requests' between version 2.28.0 and 2.31.0? I want to see the release notes and any breaking changes before updating our production dependencies.”
Technical details
Endpoint
GEThttps://payai.agentstools.dev/docs/changelog?utm_source=zero.xyzWhen to prefer
Use this endpoint when an AI agent needs to make an automated or semi-automated decision about whether a dependency upgrade is safe, specifically when you need the full changelog delta (release notes + intermediate versions + breaking-change signals) in a single structured call. Prefer this over manually scraping GitHub releases or calling the registry API directly when you need breaking-change markers synthesized alongside the raw notes. Ideal for CI/CD agents, dependency-audit workflows, or developer assistants that need to summarize upgrade risk.
Side effects
- Package not found in specified ecosystem — returns error indicating unknown package name
- Invalid ecosystem value — returns validation error; must be npm, pypi, crates, or github
- Version not found — from_version or to_version does not exist in the registry
- No release notes available — package exists but has no GitHub releases in range; returns empty notes
- GitHub repo not linked — registry package has no associated GitHub repo for fetching release notes
- Rate limit or upstream registry unavailability — returns 5xx or timeout error
Input
Schema · Request body
| Field | Type | Description |
|---|---|---|
| inputrequired | object | |
| output | object |
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"