API
API: documented, not servedThe tools on this site run in your browser and keep your data on your device. Each one is also built to run as a small, deterministic HTTP API, the programmatic counterpart to the browser tools. That API is fully implemented and documented here, but this site does not serve it. The reference below is a specification browser, not a live endpoint.
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.
What this means for your data
By design, the API would receive only the input you send it, compute a result, and return it: stateless, logging no query values or request bodies. Since the API is not served here, nothing you enter on this page is sent anywhere; the try-it panels below only show you the request you would make.
The same engine as the browser
Every endpoint runs the same pure function the in-browser tool runs, so the API and the browser return byte-identical results.
The specification
The full contract is published as OpenAPI 3.1. Download it, point your own tooling at it, or read the reference below.
Reference
Loading the specification.