API
API: documented, not served目录中的工具在你的浏览器中运行，并把你的数据留在你的设备上。每个工具还被构建为可以作为一个小型、确定性的 HTTP API 运行，即浏览器工具的程序化对应物。该 API 已完整实现并在此提供了文档，但本站并不对外提供该 API。下方的参考是一个规范浏览器，而不是实时端点。
Why the API is documented but not served here
Running a public API means paying for compute on every call, with a bill that grows with usage in ways a single maintainer cannot cap safely. This site is deliberately free and predictable to run, so it serves the browser tools (which compute on your own device, at no cost to the host) and keeps the API dormant rather than risk unbounded cost. The endpoints are real and the contract is stable; what is switched off is the hosted execution. If you need the API today, the engine is open and can be run yourself.
Self-hosting: turn the toolbox into your API
Everything needed to consume these tools as an Application Programming Interface (API) ships in the open-source repository, and the path from download to serving is deliberately short. One: download the source - github.com/ronutz/arsenal, Apache-2.0 licensed. Two: switch the API on - open src/config/apiSurface.ts and flip the single API_PROCESSING switch from 0 to 1; that one value drives both the Worker that serves the endpoints and every API badge in this interface, so the two can never disagree. Three: compile and deploy - npm install, npm run build, and publish to your own Cloudflare Workers account with the adapter already wired into the repository. Four: call the endpoints documented in the reference below - now answered by your deployment, on your domain, under your control.
That is the whole design: self-hosting plus a flip of a switch makes this an API toolbox. The same deterministic engines that power these pages answer the endpoints - tools that compute, never guess - and the switch works in both directions: set API_PROCESSING back to 0, redeploy, and the surface returns to documented-but-not-served, endpoints answering 404, badges neutral.
这对你的数据意味着什么
该 API 只接收你发送给它的输入，计算出结果并返回。它是无状态的，不记录任何查询值或请求体。如果你需要有保证的零数据外发，请使用浏览器工具，或自行运行开放引擎。
与浏览器相同的引擎
每个端点都运行与浏览器内工具相同的纯函数，因此 API 和浏览器返回逐字节一致的结果。
参考
正在加载规范。