API

API: documented, not served

Verktygen på den här webbplatsen körs i din webbläsare och håller dina data på din enhet. För automatisering – skript, pipelines och integrationer – finns samma deterministiska beräkningar tillgängliga som ett litet HTTP-API. Det är den programmatiska motsvarigheten till webbläsarverktygen, inte en ersättning för dem.

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.

Vad detta betyder för dina data

API:et tar bara emot den indata du skickar, beräknar ett resultat och returnerar det. Det är tillståndslöst och loggar inga frågevärden eller begärandekroppar. Om du behöver garanterat noll datautflöde, använd webbläsarverktygen eller kör den öppna motorn själv.

Samma motor som webbläsaren

Varje endpoint kör samma rena funktion som verktyget i webbläsaren, så API:et och webbläsaren returnerar byte-identiska resultat.

Specifikationen

Hela kontraktet publiceras som OpenAPI 3.1. Ladda ner det, rikta dina egna verktyg mot det eller läs referensen nedan.

Ladda ner openapi.yaml

Referens

Laddar specifikationen.