About Us

SMT Tooling started as a folder of single-purpose HTML files on one developer's machine. Every time an integration went sideways — a JWT that would not verify, a cron line nobody could read, a JSON response with a shape that changed on Tuesdays — a tiny page got written to answer that one question, then quietly reused for years. This site is that folder, cleaned up and made public, because the tools were never really personal. Every API developer keeps some version of the same scratch kit; we just decided to host ours where anyone can grab it.

The mission is narrow on purpose. We are not trying to be a platform or a suite. We want to be the tab you open when you need to fire a quick request, decode a token, sanity-check a regex, or format a payload — and then close without having created an account, dismissed a modal, or wondered where your data went. Every tool here runs entirely in your browser. Nothing you paste is uploaded, logged, or stored, which is the only honest way to build tools people feed real bearer tokens and staging responses into.

The editorial side is written and maintained by an engineer who spent enough years on integration and QA teams to have strong opinions about error messages and cron syntax. That editor writes the blog, tests each tool against the ugly edge cases that actually show up in production, and rewrites any explanation that reads like it was generated to fill space. If a tool on this site frustrates you, it will get fixed — that feedback loop is the whole reason the site is public rather than a private folder.

We keep the scope tight, the pages fast, and the copy written by someone who has actually debugged the thing being described. If you have found a bug, want a tool that does not exist yet, or just want to argue about regex flags, write to us at [email protected]. Real messages get real replies.