Developer infrastructure for the public web

Web access without the friction.

Proprietary web access technology designed for near-universal reach across public web pages.

No signupNo subscriptionPay only for successful requests
request pipeline

01 URL → public page

02 MODE → auto selects access path

03 RESULT → normalized response

Easy when possible. Hard when necessary.

How it works

One API for pages that need different levels of access.

01

Send a URL

Submit a public URL to the Fetch API.

02

Let Auto decide

Auto starts with the lowest-cost method and escalates only when necessary.

03

Receive the result

Get normalized content and clear billing metadata in one response.

Access modes

Easy

Fast and lightweight

For pages that do not require full browser execution. This is the lowest-cost mode, without promising universal success.

Hard

Browser-capable access

For JavaScript-heavy and difficult pages when a fuller browser path is necessary.

Start with one request

A small surface area for a practical API.

Use the API base URL configured for your environment and keep your API key on the server side.

Read the quick start
curl -X POST https://web-bypass.dev/v1/fetch \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"url":"https://example.com","mode":"auto"}'

Usage pricing

Simple rates. No monthly commitment.

See full pricing

01 / Lightweight

Easy Access

Lowest cost

$0.10

per 1,000 successful requests

Failed requests are free. Minimum balance top-up: $5.

FAQ

Useful answers before your first request.

What is Auto mode?

Auto starts with Easy and uses Hard only when the result requires escalation. You pay for the mode that successfully retrieves the page.

When is Hard used?

Hard is intended for JavaScript-heavy or otherwise difficult public pages. It is used only when necessary.

Do failed requests cost money?

No. A final failed request is free. In Auto, a failed Easy attempt followed by a successful Hard attempt is charged at the Hard rate only.

Do I need a subscription?

No. Usage is metered by successful requests, with no monthly commitment.

What content can I fetch?

The service is intended for publicly accessible web content. Do not use it to access private resources or bypass authorization.

How do I add balance?

The intended billing model uses USDT top-ups with a configured minimum. Public recharge availability is not advertised by this pre-release surface.

Do you support custom request headers?

No. The MVP Fetch API accepts a URL and an optional mode only.