Automation endpoints
JSON formatting, JWT decoding, and UUID generation endpoints that can be called from scripts, CI jobs, docs, and internal platforms.
Takeaway
The API surface should stay small, predictable, and script-friendly until usage proves which browser utilities deserve automation endpoints.
01
Current contract
The live API exposes JSON formatting, JWT decoding without signature verification, and bounded UUID generation. These routes serve automation use cases where a browser UI is not convenient, such as CI checks, shell scripts, and internal tooling.
02
Design constraints
Every endpoint should have explicit request shapes, stable JSON responses, documented error status codes, and tight limits. Utility APIs become more trustworthy when they fail clearly and avoid hidden server-side behavior.
03
Expansion criteria
New endpoints should be added only when a tool has a repeatable script use case, low privacy risk, and a bounded execution model. Hashing, date conversion, and text transforms are likely candidates once examples and limits are documented.