Changelog

​

Style guides that capture the look, not only the tokens

• components describes the treatment most panels share (border, corners, background, padding, text colour, shadow and any decorative layer such as an offset dotted shadow), the top navigation bar, how the selected and other tabs are drawn, a full-width band painted far from the page colour such as a dark hero, and whether panel titles sit on the border line, inside the panel or above it
• secondaryButton is the second call to action, painted differently from the first or only outlined
• Every button, panel, header and tab carries a css string of declarations you can paste into a rule, and css, tailwind and shadcn include the panel, header, tab, band and secondary colours as variables
• url reads one page instead of the homepage, for a section styled differently from the rest of the site, and maxAge sets how old a stored result may be. maxAge: 0 reads the page fresh
• dark holds the colours a site switches to for visitors who prefer a dark theme. It is null when we checked and the site does not change, so you know not to invent a dark palette
• shadcn is the design under shadcn/ui variable names (--background, --foreground, --primary, --card, --border and the rest), with a .dark block when the site has one. css and tailwind gain a prefers-color-scheme: dark block in the same case
• A typeface published on Google Fonts now comes with its Google stylesheet link, even when the site hosts its own copy, and the exports load it from there. files only lists a site’s own font files when there is no public source
• The button is the site’s call to action, not a dropdown or tab that happens to be the largest control. minWidth and minHeight are the size it rendered at
• Two colours never share a name. A second shade of the same colour is called, for example, “Pale Blue (darker)”
• Colours written in newer CSS formats such as oklch() are read as well. Sites built that way used to come back without text, border or button colours
• Body text size is the size most of the words are set in, not the size of the longest paragraph

​

More of the page, more often

• Pages built from cards and tiles, such as product hubs and homepages, keep their cards even when the top of the page reads like a short article
• Pages that draw their content in the browser after they load, such as a list filled in from a template or an app that keeps its text in page data, are now loaded the way a browser loads them, so that content comes back
• A page we already have is no longer thrown away because a later attempt ran into a block page
• A rate limit is no longer mistaken for a block, and a short JSON reply is returned as the answer it is rather than retried as a thin page
• A sign-in page with a “verify you are human” box is returned as the page it is, not reported as blocked

​

A subdomain answers for its company

• domain is the company’s domain, and queriedDomain is the host you asked for, so you can tell the two apart
• A subdomain with its own name, description or logo keeps its own answer
• A customer site on a hosting platform never inherits the platform’s brand

​

The right dates, and when a page was last updated

• The publication date is read from what the page declares, then from the byline beside the title. A date in a related-posts card, a sidebar or a list of other articles is no longer taken as the page’s own
• When the dates beside the title disagree, or the only date is labelled as an update, publishedTime is null rather than a guess
• modifiedTime is the date the page gives for its last update, from its declared markup or a date it labels “Last updated”. It is null when the page does not say
• With onlyMainContent: true, an article keeps the short summary paragraph directly under its title. On announcements that paragraph usually carries the key facts

​

Style guides you can paste

• css is a stylesheet: an @font-face rule for each webfont and a :root block of CSS variables for colours, fonts, the type scale, radius, shadows and spacing
• tailwind is the same set of variables as a Tailwind CSS v4 theme, so classes such as bg-accent, font-heading and text-h1 pick up the site’s design
• Only plain colours, lengths, font names and https font files make it into either one, so a page cannot write anything else into your stylesheet

​

Endpoints that only answer a POST

• method: "POST" and body send the request the endpoint expects. The body goes verbatim, and you set your own content type through headers, so JSON, form-encoded and anything else are all just a body and a header
• GET stays the default. Every existing call behaves exactly as before
• Bodies are capped at 64KB. A request body selects what an endpoint returns; anything larger is a file upload, which is a different thing and not one we do
• A POST and a GET to the same URL are cached separately, and so are two POSTs with different bodies

​

Crawl and batch are tools now

• crawl and batch start the job and hand back an id; crawl_status and batch_status read it
• logo joins them, so an agent can fetch a company’s mark without building a URL itself
• screenshot now takes the same sizing and timing options as the REST call
• Thirteen tools, all under the existing web:scrape scope, so a grant you have already approved needs no re-authorising

​

Bring your team in

• Invite people, set their role, and remove them. A removed member’s seat comes back to the plan immediately
• Sign up with an email at a company that already has a workspace and you are not turned away: you ask to join, and an owner approves or declines it from the team page
• An invitation now survives sign-in and sign-up, so following an invite link and then creating an account lands you in the right workspace instead of a new empty one
• One workspace per company domain, enforced everywhere a workspace can be created

​

Told in the product, not just by email

• Credits running low, credits exhausted, a failed payment, a cancelled plan, your logo allowance, a publishable key being used off-domain, and join requests waiting on you
• They arrive live. No reload, no polling
• Email is now something you choose per category in settings, split into account alerts and product updates, so you can turn off the newsletter without also turning off “your payment failed”

​

Colours and marks you can trust

• The primary colour now comes from the company’s own mark rather than from whatever colour the page happened to use most, and a palette leads with that colour instead of the page background
• Your operating system’s font is no longer reported as a company’s typeface
• A mark that cannot say what colour it is loses to one that can, and a saturated mark is classified as mono rather than by brightness alone
• We never serve an SVG that renders blank, which is what happened when a mark was being coloured by a stylesheet we do not have
• A domain whose certificate does not cover the bare name is retried on www rather than failing to resolve
• A styleguide that cannot read one value returns the rest instead of nothing

​

Logos you can put straight in an <img> tag

<img src="https://img.hydrafetch.com/logo/stripe.com?token=pk_your_publishable_key" alt="Stripe" />

• Publishable keys (hf_pk_) are safe to commit and safe to ship in client-side markup. They serve logos and nothing else, so a key lifted from your page source cannot scrape on your account
• Logo serves never spend credits. They have their own per-cycle allowance, so a page rendering forty logos costs forty serves and zero credits
• Lock a key to your own domains if you want, and pick the size, theme and shape per URL
• Served from the edge, so the second visitor gets it immediately

​

PDFs come back as Markdown

• Headings stay headings and tables stay tables, instead of collapsing into a flat run of text in reading order
• Works on anything with a text layer, including exports from Word, LaTeX and design tools
• Previously a PDF could come back carrying page markup rather than clean Markdown. It no longer does

​

A publication date only when the page has one

• A copyright year in a footer is no longer treated as a publication date. An undated pricing page used to come back “published 1 January” of whatever year the footer mentioned
• The same applies to the date line at the top of the Markdown: present when the page states one, absent when it does not
• Pages that declare a real date are unaffected

​

Search returns results; scraping them is opt-in

• A search costs 1 credit and returns the ranked title, url and snippet
• Set scrapeResults: true to also fetch each result, at 1 credit per page scraped, the same as scraping that page yourself
• data on each result is null unless you asked for the scrape

​

One URL, one response shape

• A single URL is answered inline, always: /scrape, /markdown, /html, /raw-html, /links and /structured
• The synchronous budget is 90 seconds. Past it you get 504 with code REQUEST_TIMEOUT, naming the budget
• The fetch keeps running in the background after a timeout, so the capture usually lands in the cache and an immediate retry is fast
• Want a job instead? Send async: true. It is opt-in now, never automatic
• Crawl and batch are unchanged: they span many URLs and can genuinely run for minutes

​

Every sync endpoint is an MCP tool

• New tools: styleguide, screenshot and images, joining scrape, map, search, extract and brand
• GET /mcp/tools lists every tool with its description, credit cost and full JSON Schema — no authentication required, so a client can see the capabilities before connecting
• Tools cost exactly what the equivalent REST call costs
• The new tools sit under the existing web:scrape scope, so an existing grant needs no re-authorising

​

Brand and styleguide

• GET /v1/web/brand returns logos suited to light and dark backgrounds, the real brand colours, name, description and social profiles. Every field states whether the company declared it or we harvested it
• POST /v1/web/brand resolves up to 50 domains in one call
• GET /v1/web/brand/search finds brands we already hold by company name or domain, so you can turn what a user typed into a domain before resolving it. Returns enough to render a picker, never resolves a new domain, and is not billed
• GET /v1/web/styleguide reads the design system a site actually paints, from computed styles in a real browser, so a colour defined through four layers of CSS variables comes back as the hex it resolved to. Colours arrive by role with contrast ratios, so they drop into a theme without guesswork

​

Billing that matches what you got

• An origin’s own error page is no longer recorded as a delivered scrape
• A response with no bytes is never treated as a success, whatever status the origin returned
• A failed render no longer discards the static capture it was meant to improve on
• Upstream failures surface as errors rather than empty 200s

​

Ask for structure when you need it

• metadata.format is now metadata.structure, reporting markdown or plain
• plain is not a failure — the default extractor optimises for capturing every word and wins on listing and forum pages — but if you wanted headings, retry with preferStructure: true
• Available on scrape, search and extract over both REST and MCP

​

See whether your webhooks landed

• GET /v1/web/crawl/{id}/deliveries and GET /v1/web/batch/{id}/deliveries
• Each delivery reports its status, attempt count, the HTTP status your endpoint returned, and why the last attempt failed
• A failed row with a 5xx means we couldn’t reach you; a 4xx means we did and you rejected it

​

Errors you can branch on

​

Trustworthy extraction

• Extract across a whole site: pass a /* scope in urls and every discovered page is merged into one result.
• New entities primitive returns normalized people, companies, and products found on a page.
• Every response reports the credits it consumed and how fresh the data is.

​

Dedicated format endpoints

• POST /v1/web/markdown for clean Markdown
• POST /v1/web/html for cleaned main-content HTML
• POST /v1/web/raw-html for unmodified page HTML
• POST /v1/web/links for a page’s links
• POST /v1/web/structured for the page’s own structured data

​

Search, crawl, and media

• Search the web and get ranked results, each scraped to clean data. Filter by time, domain, and country.
• Crawl a whole site as one asynchronous job, with completion webhooks so you do not have to poll.
• Media: capture a full-page screenshot or collect a page’s images.

​

Launch

• POST /v1/web/scrape takes one URL and returns clean Markdown and structured data.
• POST /v1/web/map discovers every URL on a site.
• Credit-based billing, charged only on success, with a live balance on every response.
• API-key authentication through the X-API-Key header.