Latest updates and improvements to FourA
Below 768px the URL row reflows into two rows, response tabs scroll horizontally, and the cookie table becomes a card grid. Hint tooltips open on tap instead of hover; iPhone SE (below 374px) gets extra shrink. The Send button is centered properly and a long URL no longer pushes the page into horizontal scroll.
Expand used to stretch the response card inside the page flow, so tall panes added body scroll and shifted the layout. It's now a fixed overlay between the sidebar and viewport edge, with panes that grow to fill the viewport. Escape closes it; one helper handles click and key paths.
Host-only cookies were leaking to subdomains. We track the Domain attribute properly now and added an HO badge in the Parsed view for the (uncommon) host-only case. Raw view matches what the upstream sent: Domain=.example.com for domain cookies, no Domain= line for host-only.
Targets that resolve to a private network range now return a 400 with a clear validation error instead of being forwarded. The check runs before any request goes out and covers reserved IPv4 and IPv6 blocks. If you accidentally pass an internal hostname, you'll see a clean error right away. Same behavior across Single, Proxy Finder, and Browser.
Point any MCP-compatible client at https://mcp.foura.ai/mcp and authenticate with your FourA API key. You will get Single, Proxy Finder, and Browser as tools your LLM can call directly. Works with Claude Desktop, Claude Code, and any other client that speaks the MCP protocol. Setup guide →
The homepage playground has a third tab for Browser, next to Use Proxy and Find Proxy. Sign in and you can run real Browser requests from the dashboard with one click.
Request and response columns now share matching tabs (UI, Body, Headers, Cookies, Raw). Each pane has its own view switcher (JSON tree, HTML tree, text), Expand stretches the response full-width, and Ctrl/Cmd+K opens find-in-pane with next/prev navigation. Copy and Download buttons sit per-pane and grab exactly what's on screen, and the Cookies tab now groups by host with filter, per-row delete, and flag badges.
The Browser endpoint accepts only eight inputs (url, userAgent, headers, cookies, proxy, timeout_ms, checkStatus, checkText). The playground had been showing extras like wait_selector and viewport that silently dropped on the wire. Every field is now schema-aligned: Browser forces GET, hides the body textarea, and the Raw tab shows the exact JSON that hits the API plus a curl reproducer.
Single and Proxy Finder were silently dropping the unblocker signature even when unblocker: true was set, so anti-bot walls that check the request signature were still bouncing requests. Fixed end-to-end — if you had unblocker: true and were getting blocked on Cloudflare-fronted sites, that is why.
Some Cloudflare sites return 200 OK but inject a background script that issues the real cf_clearance cookie a moment later. Browser used to return the page before that cookie arrived, leaving the jar empty. Now Browser waits for the cookie event, so you get a clean cf_clearance you can replay through Single or Proxy.
You can now compose and send live requests right from your dashboard. Pick one of your API keys, switch between Single, Proxy, and Browser, fill in the URL, headers, and body, then hit Cmd+Enter to fire it. The response panel shows status, timing, and size, plus body, headers, and raw views you can copy or download.
We rolled out unique Open Graph cards for all 30 existing blog posts. Links shared on Discord, LinkedIn, Slack, or Twitter now show a clean, branded preview instead of a generic favicon. New posts get their card generated automatically, with text-fitting that wraps long titles instead of cutting them mid-word.
Embedded screenshots and diagrams in blog posts now switch when you flip the light/dark toggle. No more dark images burning a hole in a bright page, or pale screenshots disappearing on a dark one.
The Older button on the blog used to send you back to page 1. Pagination now lives at /blog/page/N/ URLs with numbered navigation, so you can actually browse older posts. Thanks, Vladimir Petrov.
Browser requests were silently going through our non-JS engine for 41 days. If you saw Browser fail on Cloudflare challenges or JS-heavy sites during that window, this was why. We fixed the routing. Browser hits real Chrome on every request again.
