API
API: documented, not servedAng mga tool sa site na ito ay tumatakbo sa iyong browser at pinananatili ang iyong data sa iyong device. Para sa automation, gaya ng mga script, pipeline, at integration, ang parehong deterministic na mga kuwenta ay makukuha bilang isang maliit na HTTP API. Ito ang programmatic na katapat ng mga tool sa browser, hindi isang kapalit ng mga ito.
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.
Ano ang ibig sabihin nito para sa iyong data
Tinatanggap lamang ng API ang input na ipinadala mo rito, kinukuwenta ang isang resulta, at ibinabalik ito. Wala itong estado at hindi nagtatala ng anumang query value o request body. Kung kailangan mo ng garantisadong zero data egress, gamitin ang mga tool sa browser, o patakbuhin ang bukas na engine mismo.
Ang parehong engine ng browser
Ang bawat endpoint ay nagpapatakbo ng parehong pure function na pinapatakbo ng tool sa browser, kaya ang API at ang browser ay nagbabalik ng byte-identical na mga resulta.
Ang espesipikasyon
Ang buong kontrata ay nailathala bilang OpenAPI 3.1. I-download ito, ituro dito ang sarili mong mga kasangkapan, o basahin ang reperensya sa ibaba.
Reperensya
Niliload ang espesipikasyon.