Roborabbit API

Name: Roborabbit API API
Brand: Roborabbit API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentDeveloper ToolsTesting Qabearer8 EndpointsREST

For Agents

Trigger Roborabbit browser-automation tasks and retrieve their video recordings, screenshots, and structured run outputs through a managed bearer-authenticated API.

Quickstart

Get started with Roborabbit API in minutes using your preferred integration method.

# Add to your MCP client config (Claude Desktop, Cursor, Windsurf)
{
  "jentic": {
    "url": "https://api.jentic.com/mcp",
    "auth": "oauth"
  }
}

# Then ask your agent:
"run a browser automation task and get screenshots"

# → Jentic returns the GET /events tool with parameter schema, agent executes.

Capabilities

What an agent can do with Roborabbit API API.

Launch a stored Roborabbit task from an agent and receive a run identifier for later retrieval

Pull the structured output and screenshots produced by a completed browser-automation run

Retrieve the video recording of a Roborabbit run for a human reviewer

Inspect account state and remaining run quota before triggering a batch of tasks

GET STARTED

Start building with Roborabbit API API

Explore with Jentic

View OpenAPI Document

Jentic publishes the only available OpenAPI document for Roborabbit API, keeping it validated and agent-ready.

Jentic publishes the only available OpenAPI specification for Roborabbit API, keeping it validated and agent-ready. Roborabbit runs browser-automation tasks asynchronously and returns video recordings, screenshots, and structured outputs from each run. Define a task once, trigger it on demand, and pull back run artifacts for review or downstream processing. The API is a fit for agents that need a managed browser without operating their own headless infrastructure.

Use Cases

Patterns agents use Roborabbit API API for, with concrete tasks.

★ Scheduled Web Scrape with Visual Audit Trail

An operations team needs daily snapshots and structured data from a partner portal that has no API. They define a Roborabbit task once, then trigger it on a schedule via /v1/tasks/{uid} runs. Each run returns structured JSON, a screenshot, and a video that the team can replay if the scrape ever produces unexpected output.

POST to /v1/tasks/{task_uid}/runs to start a scrape, then GET /v1/tasks/{task_uid}/runs/{uid} until it completes and download the screenshot and video

Visual Regression Checks on a Marketing Site

A growth team wants pixel-level confirmation that key pages still render correctly after deploys. A Roborabbit task captures a full-page screenshot of each tracked URL; an agent triggers the runs after every release and compares the new screenshots against a baseline. Failures surface a video of the actual browser session for fast diagnosis.

Run the marketing-site task, fetch the resulting screenshot URL from the run object, and diff it against a stored baseline image

Form-Filling Automation Behind Login

Some workflows require submitting a form on a vendor portal that has no public API. A Roborabbit task stores the navigation steps and credentials; an agent calls the run endpoint with input variables and waits for the structured response. The recorded video is kept as evidence the submission completed.

Start a run on the form-submission task with the customer's input fields and confirm the structured output reports a successful submission

AI Agent Browser Tooling via Jentic

An AI agent that needs to drive a real browser uses Jentic to discover Roborabbit tasks by intent. Jentic returns the operation schema for triggering and reading runs, the agent executes them with managed credentials, and surfaces the structured output back to the user. No headless-browser hosting is required on the agent side.

Use Jentic to find the Roborabbit run-task operation, execute it with the chosen task UID, and parse the returned structured output

Key Endpoints

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

METHOD

PATH

DESCRIPTION

POST

/v2/auth

Exchange credentials for a bearer token

GET

/v1/account

Retrieve account metadata and quota

GET

/v1/tasks

List defined browser-automation tasks

GET

/v1/tasks/{uid}

Get details of a specific task

POST

/v1/tasks/{task_uid}/runs

Start a new run for a given task

GET

/v1/tasks/{task_uid}/runs/{uid}

Retrieve a specific run with outputs

GET

/v1/feeds

Read the workspace event feed

POST

/v2/auth

Exchange credentials for a bearer token

GET

/v1/account

Retrieve account metadata and quota

GET

/v1/tasks

List defined browser-automation tasks

GET

/v1/tasks/{uid}

Get details of a specific task

POST

/v1/tasks/{task_uid}/runs

Start a new run for a given task

Why though Jentic?

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

Credential isolation

Roborabbit bearer tokens are stored encrypted in the Jentic vault. Agents trigger task runs through Jentic without ever seeing the raw token, so browser-automation credentials stay out of model prompts.

Intent-based discovery

Agents search Jentic with phrases like 'run a browser automation task' and Jentic returns the matching Roborabbit operation, its schema, and the task UID parameter the agent needs to fill.

Time to first call

Direct Roborabbit integration: about half a day for auth, run polling, and artifact retrieval. Through Jentic: under an hour — search, load, execute.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Alternative

Browserless

Browserless gives lower-level headless Chrome control, where Roborabbit packages reusable task definitions with recordings.

Pick Browserless when the agent needs raw Puppeteer-style scripting; choose Roborabbit when stored task playbooks with video output are preferred.

Alternative

Apify

Apify runs scrapers and actors at scale, while Roborabbit focuses on task-based browser sessions with screenshots and video.

Choose Apify for high-volume scraping marketplaces; use Roborabbit when audit-trail video and structured outputs per run matter more.

Complementary

Zapier

Zapier triggers downstream workflows once a Roborabbit run completes.

Pair them when a Roborabbit run output should fan out to email, Slack, or CRM updates without writing glue code.

FAQs

Specific to using Roborabbit API API through Jentic.

Why is there no official OpenAPI spec for Roborabbit API?

Roborabbit does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call Roborabbit API via structured tooling. It is validated against the live API and kept up to date. Get started at https://app.jentic.com/sign-up.

What authentication does the Roborabbit API use?

Roborabbit uses HTTP bearer-token authentication. Call POST /v2/auth to exchange your credentials for a bearer token, then send it in the Authorization header on subsequent requests. When invoked through Jentic, the bearer token is held in the Jentic credential vault and injected at execution time.

Can I trigger a task and get back a video recording?

Yes. Start a run with POST /v1/tasks/{task_uid}/runs and then poll GET /v1/tasks/{task_uid}/runs/{uid} until the run completes. The completed run object exposes the video recording, screenshots, and structured output.

What are the rate limits for the Roborabbit API?

The spec does not declare numeric rate limits; concurrent run capacity is governed by your Roborabbit account quota, which you can read from GET /v1/account. Build agents to back off when /v1/account reports remaining capacity is exhausted.

How do I run a browser-automation task with the Roborabbit API through Jentic?

Install the SDK with `pip install jentic`. Search Jentic for `run a browser automation task`, load the schema for POST /v1/tasks/{task_uid}/runs, and execute it with the task UID and any input fields. Jentic injects the bearer credential and returns the run object.

Can I list all my saved Roborabbit tasks from an agent?

Yes. GET /v1/tasks returns every task definition in the workspace, including its UID and configuration. Agents typically call this once at the start of a session so they can choose the right task to run by name.