How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Hyperbrowser Web API

Stateless web utilities: fetch a single page, run a web search, or start a crawl. Includes `/x402` micropayment-gated variants of fetch and search for permissionless, pay-per-call usage.

Hyperbrowser Web API is one of 12 APIs that Hyperbrowser publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Web, Fetch, Search, and x402. The published artifact set on APIs.io includes API documentation and an OpenAPI specification.

This API exposes 7 operations across 7 paths, and defines 40 schemas. It is described by OpenAPI 3.2.0, at version 1.0.0.

Requests are made against a single base URL, https://api.hyperbrowser.ai.

7 operations 7 paths 40 schemas 2 GET5 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
1.0.0
Base URL
https://api.hyperbrowser.ai
Authentication
API Key
Resource Areas
1

Authentication & Security 1

Hyperbrowser Web API declares 1 security scheme for authenticating requests. An API key is passed in the header as x-api-key (ApiKeyAuth). By default, every request must be authenticated.

  • ApiKeyAuth — Account API key from app.hyperbrowser.ai

Paths & Operations 7

Across 7 paths, the API surfaces 7 operations — 2 GET, 5 POST. Each is listed below with its method, path, parameters, and response codes.

Web 7
POST
/api/web/fetch
Fetch a web page
body → 200400500
POST
/api/web/search
Search the web
body → 200400500
POST
/api/web/crawl
Start a web crawl job
body → 200400500
GET
/api/web/crawl/{id}
Get web crawl job results
3 params → 200404500
GET
/api/web/crawl/{id}/status
Get web crawl job status
1 param → 200404500
POST
/x402/web/fetch
Fetch a Web Page with X402 Payment
post-x402-web-fetch 1 param body → 200400402500
POST
/x402/web/search
Search the Web with X402 Payment
post-x402-web-search 1 param body → 200400402500

Schemas 40

The contract defines 40 schemas that model the data the API accepts and returns. The most detailed are BrandingProfile (10 properties), WebCrawlPageData (10 properties), WebSearchFilters (9 properties), WebCrawlJobResponse (8 properties). Each schema is shown below with its type and property counts.

WebCrawlJobResponse
object
8 properties 2 required
FetchOutputScreenshotOptions
object
5 properties
BrandingProfile
object
Visual brand profile extracted via DOM analysis + LLM enhancement. All fields optional; the server may return a partial profile when the LLM refuses or fails.
10 properties
FetchOutputBranding
object
1 property 1 required
FetchBrowserOptions
object
4 properties
FetchOutputOptions
object
5 properties
FetchOutputLinks
object
1 property 1 required
WebSearchResultItem
object
3 properties 3 required
FetchOutputJsonOptions
object
2 properties
FetchWaitUntil
string
StartWebCrawlJobParams
object
7 properties 1 required
WebSearchStatus
string
FetchParams
object
6 properties 1 required
FetchOutputJson
WebSearchParams
object
5 properties 1 required
WebSearchFiletype
string
PageStatus
string
FetchOutputMarkdown
object
1 property 1 required
WebSearchLocation
object
3 properties 1 required
JobStatusResponse
object
1 property 1 required
WebCrawlPageData
object
10 properties 2 required
FetchNavigationOptions
object
3 properties
FetchStealthMode
string
FetchOutputHtml
object
1 property 1 required
FetchOutputScreenshot
FetchCacheOptions
object
1 property
FetchStatus
string
FetchBrowserLocationOptions
object
3 properties
ErrorResponse
object
1 property
WebCrawlOptions
object
5 properties
FetchStorageStateOptions
object
2 properties
FetchScreenshotFormat
string
WebSearchResponse
object
4 properties 2 required
WebSearchResponseData
object
2 properties 2 required
FetchSanitizeMode
string
FetchResponse
object
4 properties 2 required
JobStatus
string
WebSearchFilters
object
9 properties
FetchResponseData
object
7 properties
ScreenConfig
object
2 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

hyperbrowser-web-api-openapi.yml Raw ↑

Other APIs Hyperbrowser publishes across the network.

Hyperbrowser Sessions API
Hyperbrowser Profiles API
Hyperbrowser Scrape API
Hyperbrowser Crawl API
Hyperbrowser Extract API
Hyperbrowser Agents API
Hyperbrowser Extensions API
Hyperbrowser Profile API
Hyperbrowser Session API
Hyperbrowser Task API
Hyperbrowser X402 API
Where this information came from

This is an independent, third-party profile of Hyperbrowser Web API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.