Browse AI API

★ Only Publicly Available OpenAPI DocumentData EnrichmentData Transformationbearer19 EndpointsREST

For Agents

Run pre-trained Browse AI robots to extract structured data from websites, schedule scraping monitors, and receive results via webhook. Useful for price monitoring, lead scraping, and competitive intelligence agents.

Install Jentic One Beta

Connect the Browse AI API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Browse AI 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://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | 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 Browse AI API.

Trigger a single extraction task on a Browse AI robot with custom input parameters

Run a robot across hundreds or thousands of input URLs in a single bulk-run request

Schedule recurring monitors that re-run a robot on a website and emit changes

GET STARTED

Start building with Browse AI API

Explore with Jentic

View OpenAPI Document

Use Cases

Patterns agents use Browse AI API for, with concrete tasks.

★ E-Commerce Price Monitoring

Retail teams build a Browse AI robot for each competitor catalogue page and then use the API to run the robots on a daily schedule. The agent calls POST /robots/{robotId}/monitors to register the cadence and POST /robots/{robotId}/webhooks so its data warehouse receives the extracted prices automatically. This replaces brittle in-house scraping code and handles JavaScript-heavy sites, captchas, and rotating proxies for free.

POST /robots/{robotId}/monitors with a daily schedule and POST /robots/{robotId}/webhooks pointing to the data warehouse ingestion URL

Bulk Lead Enrichment

Sales teams take a list of company URLs and run a Browse AI robot across all of them in a single bulk operation via POST /robots/{robotId}/bulk-runs. The robot extracts firmographic data, contact emails, and tech-stack signals, and the API returns a bulk-run ID that the agent polls (or the webhook fires) to ingest results into the CRM. A list of 5,000 URLs that would take days to scrape manually completes in hours.

POST /robots/{robotId}/bulk-runs with an array of 500 company URLs and the input parameters expected by the robot

Scheduled Job Board Monitoring

Recruiting teams build a robot that scrapes a target job board and use a Browse AI monitor to re-run it daily; the monitor emits an event when new listings appear. The agent receives the new listings via the webhook subscription and creates corresponding records in the ATS. This is a robust alternative to RSS or in-house scraping when the source site does not offer an API.

POST /robots/{robotId}/monitors with a daily schedule for the job-board robot and add a webhook so new listings post to the ATS ingestion endpoint

AI Research Agent Through Jentic

An AI research agent uses Jentic to fan out across many websites without writing scraping code itself. It searches for 'extract data from a website', loads the Browse AI task schema, and triggers POST /robots/{robotId}/tasks for each target URL. Browse AI handles the page rendering, captcha avoidance, and structured extraction, so the agent only orchestrates which robots to run and where to send the results.

Use Jentic to search 'run a Browse AI robot on a URL', load the browse.ai operation, and execute it for each URL in a research target list

Key Endpoints

19 endpoints — jentic publishes the only available openapi specification for browse ai api, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

GET

/robots

List all robots on the team

POST

/robots/{robotId}/tasks

Trigger a single extraction task on a robot

GET

/robots/{robotId}/tasks/{taskId}

Get the status and result of a task

POST

/robots/{robotId}/bulk-runs

Run a robot across many input URLs in one request

POST

/robots/{robotId}/monitors

Create a scheduled monitor that re-runs the robot

POST

/robots/{robotId}/webhooks

Subscribe a webhook for robot events

PATCH

/robots/{robotId}/cookies

Refresh stored cookies on a robot

GET

/robots

List all robots on the team

POST

/robots/{robotId}/tasks

Trigger a single extraction task on a robot

GET

/robots/{robotId}/tasks/{taskId}

Get the status and result of a task

POST

/robots/{robotId}/bulk-runs

Run a robot across many input URLs in one request

POST

/robots/{robotId}/monitors

Create a scheduled monitor that re-runs the robot

Why Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

Your Browse AI bearer token is stored once, encrypted, by your own Jentic One instance and injected as the Authorization header at execution time. It never enters the agent's prompt, logs, or context.

Intent-based discovery

Agents search Jentic by intent such as 'run a scraping robot' or 'monitor a website for changes', and Jentic returns the matching Browse AI operation with its parameter schema so the agent calls the right endpoint without browsing the reference docs.

Time to first call

FAQs

Specific to using Browse AI API through Jentic.

Why is there no official OpenAPI spec for Browse AI API?

Browse AI does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call Browse AI API via structured tooling. It is validated against the live API and kept up to date. Get started with Jentic One, the self-hosted execution layer.

What authentication does the Browse AI API use?

The Browse AI v2 API uses Bearer token authentication; the token is generated in the Browse AI dashboard and passed in the Authorization header. Through Jentic, the token is stored encrypted in your Jentic One instance and the agent receives a scoped execution token instead.

Can I run a Browse AI robot on hundreds of URLs at once?

Yes. POST /robots/{robotId}/bulk-runs accepts an array of inputs and queues a run for each, returning a single bulk-run ID. You can poll GET /robots/{robotId}/bulk-runs/{bulkRunId} for status or attach a webhook to receive each task's results as they complete.

How do I monitor a website for changes through Jentic?

Search Jentic for 'monitor a website for changes', load the browse.ai schema, and call POST /robots/{robotId}/monitors with a schedule. Subscribe a webhook via POST /robots/{robotId}/webhooks so your agent receives the diff when the monitor fires.

What are the rate limits for the Browse AI API?

The OpenAPI spec does not declare explicit rate limits; in practice Browse AI throttles per plan and per concurrent task slot. Heavy bulk runs should be sized to match the credit allowance on your Browse AI subscription rather than the API's HTTP rate ceiling.

Do I need to build robots in the UI before using the API?

Yes. The API operates pre-trained robots; you train them once in the Browse AI no-code UI by clicking through the target page. After that you can list, run, schedule, and webhook them entirely through the API.

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

Yes. Because you run Jentic One yourself, your own rules decide which Browse AI operations and credentials the agent may use. Since Browse AI puts the robot id in the URL path (/robots/{robotId}/...), you can pin the agent to a single robot so it only triggers tasks with POST /robots/{robotId}/tasks and reads their results, and nothing else. You choose the operations it may call, so write actions like creating webhooks or refreshing a robot's cookies stay off limits unless you explicitly grant them.

Browse AI API

Connect the Browse AI API to your agent

Capabilities

Start building with Browse AI API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs