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 X402 API

The X402 API from Hyperbrowser — 2 operation(s) for x402.

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

Tagged areas include x402. The published artifact set on APIs.io includes an OpenAPI specification.

This API exposes 5 operations across 5 paths, and defines 36 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.

5 operations 5 paths 36 schemas 1 GET3 POST1 PUT

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, HTTP Bearer
Resource Areas
1

Authentication & Security 2

Hyperbrowser X402 API declares 2 security schemes for authenticating requests. An API key is passed in the header as x-api-key (ApiKeyAuth). It accepts HTTP bearer tokens (JWT) (X402SessionManagement).

  • X402SessionManagement — The managementToken from the X402 session purchase response. Valid for 24 hours and scoped to that session; no API key or further payment is required.

Paths & Operations 5

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

X402 5
POST
/x402/session
Create a session with X402 payment
postX402Session 1 param body → 200400402409429500503
POST
/x402/web/fetch
Fetch a web page with X402 payment
postX402WebFetch 1 param body → 200400402500
POST
/x402/web/search
Search the web with X402 payment
postX402WebSearch 1 param body → 200400402500
GET
/x402/session/{id}
Get an X402 session
getX402SessionById 1 param → 200400401403404500
PUT
/x402/session/{id}/stop
Stop an X402 session
putX402SessionByIdStop 1 param → 200400401403404500

Schemas 36

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

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
FetchOutputMarkdown
object
1 property 1 required
FetchOutputLinks
object
1 property 1 required
WebSearchLocation
object
3 properties 1 required
FetchOutputOptions
object
5 properties
WebSearchResponseData
object
2 properties 2 required
FetchOutputJsonOptions
object
2 properties
FetchCacheOptions
object
1 property
X402SessionStatus
object
6 properties 6 required
WebSearchResponse
object
4 properties 2 required
WebSearchStatus
string
FetchOutputBranding
object
1 property 1 required
WebSearchParams
object
5 properties 1 required
FetchSanitizeMode
string
ErrorResponse
object
1 property
X402SessionResponse
object
Connection credentials and a management token for the purchased browser. Save this response; get does not reissue connection credentials. These tokens cannot a…
8 properties 8 required
FetchBrowserOptions
object
4 properties
WebSearchFilters
object
9 properties
WebSearchFiletype
string
FetchStatus
string
WebSearchResultItem
object
3 properties 3 required
FetchStorageStateOptions
object
2 properties
FetchOutputJson
FetchOutputScreenshotOptions
object
5 properties
FetchParams
object
6 properties 1 required
FetchResponse
object
4 properties 2 required
FetchWaitUntil
string
FetchStealthMode
string
FetchScreenshotFormat
string
FetchResponseData
object
7 properties
X402SessionParams
object
Optional preferences for a browser session priced at 0.10 USDC per hour, paid upfront for timeoutMinutes. Unknown fields are rejected before payment verificati…
3 properties
FetchBrowserLocationOptions
object
3 properties
ScreenConfig
object
2 properties
FetchNavigationOptions
object
3 properties
FetchOutputHtml
object
1 property 1 required
FetchOutputScreenshot

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

hyperbrowser-x402-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 Extensions API
Hyperbrowser Web API
Hyperbrowser Profile API
Hyperbrowser Session API
Hyperbrowser Task API
Hyperbrowser Images API
Hyperbrowser Sandboxes API
Where this information came from

This is an independent, third-party profile of Hyperbrowser X402 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.