RollToolsApi: a free aggregated API source for everyday app data
一个提供开发中常用数据的一个稳定聚合Api接口源，运行于独立服务器，免费，且长期维护，会持续添加新的接口！【只fork不star是很没品的】
At a glance
- What is it?
- RollToolsApi is a hosted, free API collection that returns jokes, calendars, weather, barcodes, video parsing and more. The repository is a documentation index; the real interface lives at mxnzp.com and now requires an app_id and app_secret.
- Who is it for?
- RollToolsApi fits hobby apps, prototypes and small internal tools that need a grab bag of Chinese-market data without standing up their own scrapers. It is the wrong choice for anything with a hard uptime or data-freshness contract, because the README states that music and logistics were retired when upstream sources became unstable, and the whole service is one operator's independent server.
- Can I use it commercially?
- Yes. MIT is a permissive licence: you can use, modify and sell software built on it, as long as you keep its copyright and licence notices.
- Is it still maintained?
- Yes. The repository last received commits 84 days ago.
- What is it written in?
- GitHub does not report a main language for this repository.
Answers come from the project's GitHub data, last synced on October 1, 2026, and from our analysis. They are not legal advice.
Editorial analysis
What RollToolsApi actually is, and who ends up using it
RollToolsApi is not a framework you install. It is a hosted HTTP service that bundles dozens of small data lookups behind one domain, and the GitHub repository is a documentation index for that service rather than the service's source code. The README describes it as "一个提供开发中常用数据的一个稳定聚合Api接口源", running on an independent server, free of charge, and maintained long term with new interfaces added over time. The first successful third-party call is dated 2018-11-19 in the README.
The audience is narrow and practical: solo developers and small teams building an app or a demo who need a calendar, a joke list, a weather lookup or a barcode image without signing up for several vendors. The README also points at a separate project, duanzile-open-api, for anyone who wants to build a joke app on published data. If you are running a production system with an SLA, this is not aimed at you, and the README does not pretend otherwise: it is one person's server, upgraded many times, with a user chat group used to announce maintenance windows.
How requests flow: host, app_id and app_secret
Every call goes to a host plus the /api segment, then the endpoint path. The README is unusually blunt about this, saying the most common question it receives is a 404, and that the correct host is https://www.mxnzp.com/api rather than the bare domain. HTTPS is supported and recommended; the older http://www.mxnzp.com/api still works according to the README.
Authentication changed over time. Non-app_id requests were cut off on 2020-04-01, and the README states that all non-app_id requests are intercepted. The current scheme takes two parameters, app_id and app_secret, either appended to the query string or, preferably, sent as request headers. The README gives the header form as app_id=你的app_id&app_secret=你的app_secret. The stated benefit of app_id mode is fewer restrictions: you may call from your own server and you are not IP-banned for it. A temporary app_id can be obtained through the mini program for testing, and the README says it resets in the early hours of the next day, invalidating the previous one.
Data flow is therefore simple: your client sends an authenticated request, the operator's server resolves the upstream source, and you get back structured data in the shape documented for that endpoint. There is no SDK, no client library and no local component in this repository.
Installing nothing: registering an app_id and making a first call
There is no install step in the usual sense. The repository holds a README, a LICENSE, a png/ directory with QR images and a dump.rdb file; the README itself is the entry point and directs readers to https://www.mxnzp.com/doc/list for per-endpoint parameters and response examples. So the first task is credential registration, not installation.
According to the README, you scan the mini program code (or search for 电点科技), open the 我的 page, bind a phone number, and your app_id and app_secret appear. A temporary app_id for testing is obtained the same way through the 我的 tab.
Once you have credentials, the documented pattern is to add the two parameters to the request. The README's own example of a well-formed request is:
https://www.mxnzp.com/api/xxxxxThat is the shape to copy: the domain, the /api segment, then the endpoint path taken from the documentation page. If the host is truncated to https://www.mxnzp.com without /api, the README says you should expect a 404.
To verify the credentials are wired up correctly, the README describes a second check: open the mini program, go to 我的, and tap 数据统计. If the configuration is right, your calls show up there as usage statistics. That is the closest thing to a health check the project documents.
The endpoint catalogue has grown, and shrunk, unevenly
The changelog is the most informative part of the repository. Growth is steady and recent: the 2026-07-09 entry lists Douyin data endpoints (video detail and watermark removal, search, comments, follower profiles, trending lists), Xiaohongshu content parsing, Kuaishou watermark removal, AI chat and image generation, AI image recognition, SMS verification codes, WeChat group notification, live dynamic QR codes and a food-calorie V2 endpoint. Older entries add recipe, idiom, xiehouyu, story, oil price and ICP filing lookups.
Attrition is documented too, and this is the part worth reading before you commit. The same 2026-07-09 entry states that the music endpoints and the logistics query endpoints were stopped and taken offline because their upstream data sources were no longer stable, with the documentation kept only as a historical record. Several older interfaces moved to v2 or v3 versions, and the online custom parameter feature was rebuilt as remote_config. The national city list was replaced by a multi-level region interface covering province, city, district, street and village.
That pattern tells you what kind of dependency this is. The operator is bundling third-party data, so when an upstream breaks, an endpoint can disappear. The README does not document a deprecation window or a rollback path for retired endpoints.
Where RollToolsApi is the wrong tool
The service is free, single-operator and hosted on one independent server. The README states that each server upgrade requires care because it affects users, and that maintenance windows are announced in the chat group precisely so people can prepare. That is a candid description of the risk: downtime and change notices arrive through a group chat and a WeChat account, not through a status page or a versioned API contract.
Two concrete failure modes follow. First, upstream-dependent endpoints can be withdrawn, as the music and logistics interfaces were. If your product's core feature is Douyin watermark removal or a Xiaohongshu parse, you are one upstream change away from a broken build with no documented fallback. Second, IP bans exist for callers whose logic the operator considers incorrect, and the README points to a self-service unban flow through the WeChat account 《Cretin的开发之路》. A service that needs a self-service unban procedure is telling you that rate-limit mistakes are expected.
If you need contractual uptime, per-endpoint deprecation guarantees, or data you can cache and own, look elsewhere. If you need a quick source of incidental data for a side project, the trade-off is reasonable.
How it compares with running your own data layer
The obvious alternative is not another aggregator but your own thin service: you pick the upstream sources you care about, wrap them in your own endpoints, and cache the results in your own database. The difference in approach is ownership. With RollToolsApi you inherit one operator's choices, including which endpoints exist this quarter and which were retired when a source went bad, and you inherit the app_id and app_secret scheme the README mandates. With your own layer you inherit the scraping and maintenance work that the operator is currently absorbing for you.
A second alternative is the project's own sibling, duanzile-open-api, which the README presents as an open data and interface set for building a joke app. That is narrower and more concrete than the general catalogue: if your product is a joke or entertainment app, the dedicated dataset is a better fit than pulling one endpoint out of a general aggregator.
The honest framing is that RollToolsApi trades control for speed. You get a working endpoint in minutes and accept that the operator decides when it changes.
Licence, maintenance and the cost of upgrading
The repository is MIT licensed, so the README and any files in this repository can be reused under those terms. That is worth stating precisely: MIT covers the repository contents, not the hosted service. The interface itself is governed by the operator's own rules, including the app_id requirement, the IP-ban policy and the free-but-unsupported nature of the offering. Nothing in the README grants a licence to the data returned by the endpoints, and the README does not discuss data licensing at all. If you plan to redistribute endpoint data commercially, that question is unanswered here and belongs with the operator, not with the MIT file.
Maintenance is real but informal. The last push to the repository was on 2026-07-09, and that commit was a documentation sync covering interfaces added since 2024. The README says the service has run since 2018-11-19 and that the server has been upgraded more than a dozen times. Upgrade cost for you is the cost of tracking the documentation page: endpoints gain v2 and v3 variants, some are renamed, and some are removed. There is no changelog feed or API version negotiation described in the README, so the practical upgrade process is re-reading https://www.mxnzp.com/doc/list when something breaks.
Editorial conclusion
RollToolsApi fits hobby apps, prototypes and small internal tools that need a grab bag of Chinese-market data without standing up their own scrapers. It is the wrong choice for anything with a hard uptime or data-freshness contract, because the README states that music and logistics were retired when upstream sources became unstable, and the whole service is one operator's independent server. Before writing code, register an app_id and app_secret through the 电点科技 mini program, then confirm the exact host and path for your chosen endpoint against https://www.mxnzp.com/doc/list, since the README blames most 404 reports on callers omitting the /api segment.
Frequently asked questions
Does RollToolsApi need an app_id and app_secret?
Yes. The README states that non-app_id requests stopped being served on 2020-04-01 and that all non-app_id requests are intercepted. You add app_id and app_secret either as query parameters or, preferably, as request headers.
Why does a RollToolsApi request return 404?
The README names this as the most frequently asked question and attributes it to a wrong host. The host is the domain plus /api, so a correct request looks like https://www.mxnzp.com/api/xxxxx rather than the bare domain.
How do I get a RollToolsApi app_id for testing?
Scan the mini program code shown in the README, or search for the 电点科技 mini program, then open the 我的 tab and request a temporary app_id. The README says the temporary app_id resets in the early hours of the next day, after which the previous one stops working.
Are all RollToolsApi endpoints still available?
No. The 2026-07-09 changelog entry states that the music endpoints and the logistics query endpoints were stopped and taken offline because their upstream data sources became unstable, with the documentation kept only as a historical record.
Can I check whether my RollToolsApi calls are being counted?
The README describes a statistics view: open the 电点科技 mini program, go to 我的, and tap 数据统计. If the app_id is configured correctly, your calls appear there as usage data.
Official sources
Add this badge to your README
If you maintain this project, the badge below links readers to this analysis and shows its maintenance status from the daily GitHub snapshot. Paste the markdown into your README; add ?metric=license or ?metric=stars to the image URL for a different field.
[](https://hysenlabs.com/projects/mzcretin-rolltoolsapi)