HTTP Client
Send HTTP requests from your Windows machine through a local companion, with no account or MyDevTools proxy.
Requests go directly from your Windows machine to the target
Windows companion setup
Download and launch the Windows local companion required by this tool, then return to this page.
- About the Windows companion and download
- Launch MyDevTools Agent; its icon appears in the Windows system tray.
- Open the agent window from the tray icon and copy the displayed pairing code.
- Enter the code below. If the browser asks for local-network access, allow it for this connection.
Requests accept up to 1 MiB bodies, responses up to 16 MiB, and timeouts up to 120 seconds.
Private, loopback and LAN targets are blocked by default. Restart the companion with --allow-private only when you intentionally need them. HTTP pairing grants only http.request; it never grants future scanner permissions.
The browser sends request details only to the companion on 127.0.0.1. The companion connects directly to the target; target URLs, headers and bodies can therefore leave your machine. MyDevTools servers do not receive or proxy them, and this page does not persist pairing codes, requests or responses.
Local companion
Enter the fresh code from the companion window. It is cleared after every attempt.
Request
One Name: value header per line. Authorization is sent only when you enter it here.
Raw text or JSON, encoded as UTF-8. Set Content-Type explicitly when needed.
Connect and send a request to see its response.
Response headers
Body preview
On this page
Send HTTP and HTTPS requests without creating an account or routing API credentials through a MyDevTools server. A small companion running on your Windows computer performs the network request and returns status, timing, headers and the response body to this page.
Detailed Functionality
The browser pairs explicitly with the companion on 127.0.0.1 using a short-lived one-time code. The resulting session token stays in memory and grants only the http.request capability. Requests go from the companion directly to the target. Public targets are allowed by default; private, loopback and LAN addresses require the deliberate --allow-private startup option. Redirects are off by default and sensitive headers are removed when a redirect changes origin.
Practical Examples
Use GET to inspect a JSON endpoint, POST with Content-Type: application/json to test an API payload, or HEAD to inspect response metadata without a body. Add Authorization: Bearer … only when the target API requires it; it is sent to that target, not to MyDevTools servers.
How to Use This Tool
Install and start the companion
Download the Windows x64 companion and launch it.
Pair explicitly
Request a code in the companion window, enter it here and click Connect. The code is cleared immediately after the attempt.
Compose the request
Choose a method, enter an HTTP or HTTPS URL, then add optional headers and a raw UTF-8 body.
Send and inspect
Send the request to view native status, timing, final URL, duplicate-preserving headers and a safe text preview. Download binary bodies byte-for-byte.
Tips and Best Practices
- Keep redirects off when you need to inspect the first response.
- Credentials in an
Authorizationheader go to the target service; avoid sharing screenshots that contain them. - Leave private-network access disabled unless you deliberately test a trusted LAN service.
- Pairing this tool never authorizes future port or network scanning capabilities.