Recipe Builder: Chain Text and Data Tools Together
Chain decoders, formatters and converters into one reusable recipe.
Steps
No steps yet. Add one below; each step works on the previous step's output.
Use via API
Run text through a chain of PithLab operations in order (decode, format, convert, change case, sort, dedupe, hash…) and return each step's output. Send JSON, get JSON back.
POST https://pithlab.com/api/v1/tools/recipe-builder
curl https://pithlab.com/api/v1/tools/recipe-builder \
-H "Authorization: Bearer $PITHLAB_KEY" \
-H "Content-Type: application/json" \
-d '{"input":"eyJiIjoxLCJhIjoyfQ==","steps":"base64-decode,json-format,hash:SHA-256"}'About the Recipe Builder
Chain encoders, decoders and converters into one recipe: Base64 decode, format JSON, convert to YAML and more. Share it as a link. Runs in your browser.
How to use the Recipe Builder
- Paste your input text.
- Add steps in the order they should run, for example Base64 decode and then Format JSON.
- Check each step's output; if one fails, the error says which step and why.
- Copy the final result, or copy a share link that rebuilds the same recipe.
Examples
Input
eyJuYW1lIjoiUGl0aExhYiIsInRvb2xzIjo1fQ== → Base64 decode → Format JSON
Output
{
"name": "PithLab",
"tools": 5
}Input
Hello World PithLab Tools Hello World → Remove duplicate lines → Slugify each line
Output
hello-world pithlab-tools
Input
hello%20world → URL decode → Hash (SHA-256)
Output
b94d27b9934d3e08a52e52d7da7dabfac484efe37a5380ee9088f7ace2efcde9
Frequently asked questions
Is this like CyberChef?
Yes, it borrows CyberChef's best idea: piping one operation's output into the next. It focuses on the everyday steps (encoding, decoding, JSON, YAML, CSV, case, lines and hashes) with a simpler interface that works well on phones.
Is my data uploaded?
No. Every step runs in your browser using the same code as PithLab's individual tools. A share link stores the recipe and input in the part of the URL after #, which browsers never send to a server.
What happens when a step fails?
The recipe stops at that step and shows its error, for example invalid JSON. Earlier steps still show their output so you can see where things went wrong.