Virix Labs · OAuth Scopes

Virix Labs OAuth Scopes

OAuth 2.0 searched

Virix Labs publishes 5 OAuth 2.0 scopes via the clientCredentials and authorizationCode flows. Scopes are the fine-grained permissions an application requests at authorization time to act against the Virix Labs API on a user’s behalf.

Tokens are issued from https://agent.humanbrowser.cloud/oauth/token.

This index is generated from the provider’s OpenAPI security definitions (and, where available, its documented scope reference) and refreshes on every APIs.io network build. Browse every provider’s scopes at scopes.apis.io.

Browser AutomationCloud BrowserAI AgentsA2AMCPWeb ScrapingResidential ProxiesCAPTCHA SolvingHuman-in-the-LoopComputer UseAgent-NativeUnited Kingdom

Scopes: 5 Flows: clientCredentials, authorizationCode Method: searched

OAuth endpoints

Authorization URL
https://agent.humanbrowser.cloud/authorize

Token URL
https://agent.humanbrowser.cloud/oauth/token https://agent.humanbrowser.cloud/token

Flows
clientCredentialsauthorizationCode

Scopes (5)

Scope	Description	Flows
session:run	Spawn and drive browser sessions	clientCredentials
account:read	Read token balance, usage and account state	clientCredentials
account:topup	Create top-ups / purchases against the account	clientCredentials
mcp:run	undocumented — by name, invoke MCP tools that run browser tasks	authorizationCode
mcp:read	undocumented — by name, read-only MCP access	authorizationCode

📄 Provider scope reference: https://agent.humanbrowser.cloud/.well-known/oauth-authorization-serverhttps://agent.humanbrowser.cloud/.well-known/oauth-protected-resource

Source

OAuth Scopes

generated: '2026-09-19'
method: searched
source: openapi/humanbrowser-cloud-openapi.json
docs:
- https://agent.humanbrowser.cloud/.well-known/oauth-authorization-server
- https://agent.humanbrowser.cloud/.well-known/oauth-protected-resource
summary: >-
  Two scope vocabularies from two OAuth surfaces that do not reference each other. The OpenAPI's oauth2
  clientCredentials scheme declares session:run, account:read and account:topup and binds them per
  operation — but its tokenUrl (https://agent.humanbrowser.cloud/oauth/token) 404s on GET and POST. The
  live authorization server's RFC 8414 metadata on the same host declares mcp:run and mcp:read for the
  MCP resource, with no per-tool binding published anywhere. Neither vocabulary is documented on a
  scopes/permissions page (/docs/oauth 404). Every shipped integration uses the unscoped hb_live_ bearer
  token instead.
schemes:
- name: oauth2
  source: openapi/humanbrowser-cloud-openapi.json
  flows:
  - flow: clientCredentials
    tokenUrl: https://agent.humanbrowser.cloud/oauth/token
    tokenUrl_status: 404 (GET and POST, 2026-09-19)
  description: Least-privilege scoped access. Request only the scopes an agent needs.
- name: mcp-oauth
  source: well-known/humanbrowser-cloud-oauth-authorization-server.json
  flows:
  - flow: authorizationCode
    authorizationUrl: https://agent.humanbrowser.cloud/authorize
    tokenUrl: https://agent.humanbrowser.cloud/token
    pkce: S256
  description: RFC 8414 metadata; resource https://agent.humanbrowser.cloud/mcp per RFC 9728.
scopes:
- scope: session:run
  description: Spawn and drive browser sessions
  flows:
  - clientCredentials
  operations: [runA2ATask]
  sources:
  - openapi/humanbrowser-cloud-openapi.json
- scope: account:read
  description: Read token balance, usage and account state
  flows:
  - clientCredentials
  operations: [getAccount, getUsage]
  sources:
  - openapi/humanbrowser-cloud-openapi.json
- scope: account:topup
  description: Create top-ups / purchases against the account
  flows:
  - clientCredentials
  operations: [topUp]
  sources:
  - openapi/humanbrowser-cloud-openapi.json
- scope: mcp:run
  description: undocumented — by name, invoke MCP tools that run browser tasks
  flows:
  - authorizationCode
  operations: []
  sources:
  - well-known/humanbrowser-cloud-oauth-authorization-server.json
  - well-known/humanbrowser-cloud-oauth-protected-resource.json
- scope: mcp:read
  description: undocumented — by name, read-only MCP access
  flows:
  - authorizationCode
  operations: []
  sources:
  - well-known/humanbrowser-cloud-oauth-authorization-server.json
  - well-known/humanbrowser-cloud-oauth-protected-resource.json

Work with this as data

Every scope set here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for oauth scopes

4 MCP tools reach this

find_scopesBrowse and filter every scope set in the catalog.
apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
resolveTurn a domain, URL or GitHub org into the provider it belongs to.
find_cohortsEvery scored population of providers in the catalog.

All 92 tools →

Call it yourself

curl for this page

This scope set

curl "https://apis.io/api/v1/scopes/humanbrowser-cloud-scopes"

All oauth scopes

curl "https://apis.io/api/v1/scopes?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.