About
A scraping API from the team that also runs its screenshot engine.
Webfetch is built and operated by Tuxxin LLC,
an IT company that has been in business for nearly 16 years; its founder has been part of
several successful startups. Webfetch itself is new.
The fetch engine, the proxy routing, billing and the key portal are ours, running on
our own framework (TiCore, credited in this page's own markup), on hardware we
provision. When you set screenshot on a request, our renderers capture it
in the same page load and it comes back as a link at no extra credit cost. If they
cannot take it, the capture is handed to
webshot.site, a sister product from
the same operator.
What we run
Tuxxin LLC operates webfetch.io and webshot.site as separate products: separate domains, separate pricing, separate signups. Webfetch calls webshot.site's own public API as a screenshot fallback, the way any other customer would. The two share an operator; each has its own codebase.
Who builds it
Webfetch is new; the company behind it is not. Tuxxin LLC has been running Linux infrastructure and building software for small and medium businesses for nearly 16 years. Its founder and principal engineer, Daniel Jones, has been writing code since 2001 and has been part of several successful startups. He built the TiCore framework this site runs on, and his security research tools work the same ground a scraping API does: worldip.io maps the ownership and location of the whole IPv4 space, and whack.sh loads a link through datacenter, residential and mobile networks at once to catch sites that show automated visitors something different from people.
Why webfetch exists
A page that renders behind JavaScript, sits behind a bot check, or needs to come back as structured data instead of raw markup is a common problem with an inconsistent set of solutions. Webfetch is one endpoint that covers the range: a plain HTTP fetch when that's enough, a headless browser when it isn't, a proxy pool when the target is actively defended, and a rules engine that turns the result into JSON instead of leaving you to parse it.
-
You're billed for what worked.
A failed fetch writes 0 to the credit column on the request row at the moment it fails. There's no refund queue because nothing was charged to refund. -
robots.txt is honored by default, on every request.
Turning it off needs an account, needs the acceptable use policy accepted on that key, and is logged per request. -
The free tier keeps going.
You start with 1,000 credits, and 250 more arrive on the 1st of every month, banking up to 1,000, for as long as the account exists.
How a credit is priced
Every plan is 38 to 40% below the equivalent ScrapingBee plan for
the same monthly credit allowance, computed from the same numbers your invoice is,
not typed as a marketing figure. That range is where it is for a specific reason: a
rendered request through the stealth exit pools (stealth_proxy)
costs us real, metered bandwidth priced by the gigabyte, and that cost is flat per
request while a competitor's price per credit falls steeply on their higher tiers.
Discount much further and the thinnest paid plan stops covering its own stealth
traffic on an ordinary page; the number here is set so it comfortably does.
The same logic is what "price locked for life" commits to: the price you sign up at is the price you keep for as long as your payment method stays active and the subscription doesn't lapse, because the price was never a promotional number to begin with. It's the number the economics were built around.
Talk to us
Product questions, a custom plan, or a scraping report against a key: the contact form reaches the same team that runs the API.