About
Tool No. 44 of Pikkola
A curl command is one line that carries six things at once: a method, an address, a query string, headers, credentials and a body. Written by hand it is readable to the person who wrote it and to almost no one else, and the line that arrives in a ticket is usually the one nobody wants to rewrite. This page takes it apart, shows each part where curl would put it, writes it back out, and gives the same request to eight clients.
What it does
- Reads the line the way a shell hands it over: single and double quotes, a backslash at the end of a line, a value attached to its flag, a cluster of short flags, and a prompt copied along with the command.
- Shows the method, the address and its query, the headers, the credentials and the body as separate parts, with a JSON body printed in full and a multipart body listed field by field.
- Rebuilds the command from a visual builder, with quoting that survives another trip through a terminal.
- Generates the same request as JavaScript fetch, TypeScript fetch, Axios, Python requests, Python httpx, Go net/http, Node undici and HTTPie.
- Names what it could not read honestly. A variable, a file body, an unknown flag: each is written in the notes instead of being guessed at.
- Five presets for the shapes people paste most: a REST JSON POST, a bearer token GET, a GraphQL query, a multipart upload and a signed webhook.
What the rebuild changes
The request stays the same. The text does not, and it is worth knowing why. Flags are written in one order, one per line, so a diff of two commands shows what actually changed. Quoting is made safe: a value with a space or an apostrophe is quoted so the shell passes it through whole. --request GET is left out, because GET is what curl does when nothing is said, and flags the page does not read are dropped and named in the notes.
What it deliberately does not do
It does not send the request. A live request is a test against someone else's server, and a test belongs to a tool you already trust, with your cookies and your network. It does not fetch a URL, resolve a host, or check whether an endpoint exists. It does not tell you whether a key is valid, and it cannot tell whether a string is a secret: a key pasted into a command is already in the shell history, and the page says so rather than hiding it.
Where the draft lives
In this browser's local storage, under one key, so a reload does not lose work. Nothing is sent anywhere. The page's own content policy sets connect-src to none, which means a request could not leave even if one were attempted.
Questions and corrections: [email protected]