curl-native developer tools
Developer tools
you already
curl.
UUIDs, hashes, JWTs, CIDR math, SSL and WHOIS lookups, pastes and throwaway webhooks — each one is just a URL. Run it with the curl you already have — clean text in your shell, a real documented page in your browser.
curl curlhub.sh/uuid
copy · run · done — no signup, no install, nothing to keep
the toolbox
Two dozen small, sharp tools.
Each does one thing well and returns exactly what you'd want to see in a terminal. Here's the whole set — browse them all →
Generate & transform
Inspect & look up
Ephemeral https only
Reference
how it's built
Boring on purpose. Careful where it counts.
A tool you reach for daily should be predictable, private, and honest about its trade-offs.
01 Same URL, two audiences
Hit a tool with curl and you get terminal-ready text and ANSI. Open the same URL in a browser and you get a documented page with runnable examples. No ?format gymnastics.
02 Quiet by default
No accounts, no ad networks, and no profile built from your requests — the pure tools don't keep what you send them. The stateful ones — pastes, file drops, webhooks — hold data only until they expire. (Infrastructure and Cloudflare log request IPs, and our cookieless analytics count aggregate page views, as most sites do — the details are on Privacy.)
03 Nothing to install, nothing to update
It's just a URL and the curl you already have — no client to install, version, or keep current. Drop a request into a script, a container, or a CI job and it runs the same everywhere.
04 Docs the crowd keeps sharp
The /man wiki is community-edited man pages and recipes — thousands of commands, kept sharp by the people who use them. Per-tool voting and suggestions are opening to verified accounts next.
the front door
Type curl curlhub.sh and start there.
The bare domain prints a menu — every tool, grouped, with a couple of copy-paste starters. It's the same directory as this page, rendered for the shell.
Jump to the tools