Install Jentic One Beta

Connect the Browserbase API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Browserbase API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.

Step 1: Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fbrowserbase.com%2Fbrowserbase" | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fbrowserbase.com%2Fbrowserbase" | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with Browserbase API.

Create and control cloud headless browser sessions

Manage reusable browser contexts for persistent state

Upload and manage browser extensions for sessions

Retrieve session logs, recordings, and downloads

Get live debug URLs and project usage details

GET STARTED

Start building with Browserbase API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use Browserbase API for, with concrete tasks.

★ Cloud browser automation

A scraping or automation workflow needs a real browser it does not have to host. The Browserbase API creates a session in the cloud, returns control and debug URLs, and cleans up when done, so a backend runs browser tasks without managing infrastructure.

Create a session via POST /v1/sessions and return its live debug URL for the automation client

Persistent context reuse

Automations that log in once and reuse the state need persistent contexts. The context operations create and update reusable contexts so a session can start already authenticated instead of repeating a login.

Create a context via POST /v1/contexts and attach it when creating a new session

Session observability

Debugging an automation requires visibility into what the browser did. The session operations expose logs, recordings, and downloads so a developer can inspect a run after it completes.

Retrieve logs via GET /v1/sessions/{id}/logs and the recording via GET /v1/sessions/{id}/recording

AI agent web automation

An AI agent that browses the web can run real sessions without hand-wiring the Browserbase key. Through Jentic the agent discovers the session operations by intent and calls them with the stored credential.

Search Jentic for 'start a headless browser session', load the schema, and open a session for a browsing task

Key Endpoints

18 endpoints — the browserbase api runs headless browser sessions in the cloud for automation and scraping.

METHOD

PATH

DESCRIPTION

POST

/v1/sessions

Create a headless browser session

GET

/v1/sessions

List browser sessions

GET

/v1/sessions/{id}

Retrieve a single session

POST

/v1/contexts

Create a reusable browser context

GET

/v1/sessions/{id}/logs

Retrieve the logs for a session

GET

/v1/sessions/{id}/recording

Retrieve the recording for a session

POST

/v1/sessions

Create a headless browser session

GET

/v1/sessions

List browser sessions

GET

/v1/sessions/{id}

Retrieve a single session

POST

/v1/contexts

Create a reusable browser context

GET

/v1/sessions/{id}/logs

Retrieve the logs for a session

GET

/v1/sessions/{id}/recording

Retrieve the recording for a session

Why Jentic?

What agents get from Jentic-routed access to this vendor.

Setup

Wiring the Browserbase API by hand means setting the X-BB-API-Key header on every request and shaping the session, context, and extension payloads yourself. Through Jentic you install once, import the API from the API Directory, store your credential once, and your agent calls it.

Permission scoping

The Browserbase API addresses sessions, contexts, and extensions by id in the URL path, so you can limit the agent to the operations it needs, such as creating a session or reading its logs. You credit the agent only with the operations you allow, so deleting an extension stays out unless you add it.

Credential isolation

Your the Browserbase credential is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.

Intent-based discovery

Agents search Jentic by intent such as 'start a headless browser session', and Jentic returns the matching Browserbase operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

FAQs

Specific to using Browserbase API through Jentic.

What authentication does the Browserbase API use?

The Browserbase API authenticates with an API key sent in the X-BB-API-Key header. Through Jentic the key is stored encrypted in your own instance and injected into each request at run time.

Is there a the Browserbase API MCP server?

You don't need an MCP server to give your agent the Browserbase API. Jentic connects it directly from the API Directory: import it, store your credential once, and your agent calls it. That keeps another server's tool definitions out of your agent's context while still giving it the operation set from the spec.

Can I reuse a login across Browserbase sessions?

Yes. Create a context with POST /v1/contexts to persist browser state such as cookies, then attach that context when you create a session so it starts already authenticated.

Can I limit what my agent is allowed to do with the Browserbase API?

Yes. Because you run Jentic One yourself, your own rules decide which the Browserbase API operations and credentials the agent may use. You grant only the operations it needs, such as creating a session, so deleting an extension stays off limits unless you add it. The choice of what the agent may call is yours.

How do I connect my agent to the Browserbase API through Jentic?

Search Jentic by intent such as 'start a headless browser session' to discover the operation, load its input schema, and your agent calls it with your stored credential injected at run time. To run it on your own infrastructure, install Jentic One from its GitHub repo.

Browserbase API

AI ReadinessFoundational (D)44/100

See full scorecard

Official vendor OpenAPI document · agent-readyCloud InfrastructureComputeapiKey18 EndpointsREST

For Agents

Create and control cloud headless browser sessions, manage contexts and extensions, and retrieve session logs, recordings, and downloads.

Use for: I need to start a headless browser session in the cloud, List my active browser sessions, Create a reusable browser context, Get the live debug URL for a session

Not supported: Does not handle proxy management, CAPTCHA solving, or data storage - use for running and inspecting cloud headless browser sessions only.

The Browserbase API runs headless browser sessions in the cloud for automation and scraping. It creates and controls sessions, manages reusable contexts and browser extensions, and exposes session logs, recordings, downloads, and live debug URLs. Requests authenticate with an API key sent in the X-BB-API-Key header.

Jentic One on Github View OpenAPI Document

Show dimension breakdown

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: A+Signals: 4

98%

Lint Results

Aggregated quality score from linter diagnostics, weighted by severity.

100%

Resolution Completeness

Percentage of `$ref` references that resolve successfully.

100%

Specification Validity

Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).

100%

Structural Integrity

Structural correctness score based on schema issues using logarithmic dampening.

Developer Experience & Jentic Compatibility

Clarity, completeness, and ingestion readiness for developers and tooling.

Grade: C+Signals: 4

Example Density

How richly the API is illustrated with examples.

100%

Example Validity

Percentage of examples that conform to their schemas.

31%

Response Coverage

Percentage of operations with complete response definitions (success, client error, server error).

100%

Tooling Readiness

Health of API ingestion, bundling, and resolution within Jentic pipelines.

AI-Readiness & Agent Experience

Semantic breadth, depth, and agent comprehension for AI systems.

Grade: FSignals: 4

29%

Description Coverage

Coverage of descriptions across API elements.

Error Standardization

Coverage of RFC 9457 Problem Details for error responses.

OperationId Quality

Coverage, uniqueness, and casing consistency of operationIds for AI inference.

56%

Summary Coverage

Coverage of summaries across operations/tags/info.

Agent Usability

Functional utility, complexity comfort, and AI orchestration readiness.

Grade: A+Signals: 1

94%

Complexity Comfort

Agent comfort level based on API operational and structural complexity.

Security

Trust, risk posture, and security compliance.

Grade: C-Signals: 1

50%

Authentication Strength

Average quality of security schemes based on authentication method strength (weakest link for OAuth2).

AI Discoverability

Findability, semantic richness, and reasoning readiness.

Grade: D-Signals: 1

40%

Descriptive Richness

Clarity and depth of descriptions across API elements.

Connect the Browserbase API to your agent

Capabilities

Start building with Browserbase API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

Browserbase API

Jentic AI Readiness Score

Browserbase API

Foundational Compliance

Lint Results

Resolution Completeness

Specification Validity

Structural Integrity

Developer Experience & Jentic Compatibility

Example Density

Example Validity

Response Coverage

Tooling Readiness

AI-Readiness & Agent Experience

Description Coverage

Error Standardization

OperationId Quality

Summary Coverage

Agent Usability

Complexity Comfort

Security

Authentication Strength

AI Discoverability

Descriptive Richness