canonical: https://jentic.com/apis/roborabbit.com/roborabbit

# Roborabbit API

Roborabbit API for browser automation tasks. Runs tasks asynchronously with video recordings, screenshots, and structured outputs. The API exposes 8 endpoints secured with bearer authentication.

## For AI agents

Programmatically verify authorization status, check quota and usage metrics. Covers 8 operations with bearer authentication.

## Scope

Does not handle payments, communications, or crm - use for hr and recruiting only.

## Capabilities

- Verify authorization status
- Check quota and usage metrics
- List all tasks
- Retrieve specific task details
- Execute a task

## Use cases

### HR and Recruiting Operations

Use the Roborabbit API to perform hr recruiting operations programmatically. The API provides 8 endpoints covering core functionality including verify authorization status, check quota and usage metrics, list all tasks.

Example prompt: Call GET `/v2/auth` to verify authorization status

### Automated v1 Management

Automate v1 operations by combining multiple Roborabbit API endpoints. Agents can check quota and usage metrics and then list all tasks in a single workflow.

Example prompt: Call GET `/v1/account` to check quota and usage metrics, then verify the result

### AI Agent Integration via Jentic

AI agents discover and call Roborabbit API endpoints through Jentic without managing credentials directly. An agent searches for the required operation by intent, receives the matching endpoint schema, and executes the call with Jentic-managed authentication. This eliminates the need to read API documentation or handle bearer tokens manually.

Example prompt: Search Jentic for 'verify authorization status', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| GET | `/v2/auth` | Verify authorization status |
| GET | `/v1/account` | Check quota and usage metrics |
| GET | `/v1/tasks` | List all tasks |
| GET | `/v1/tasks/{uid}` | Retrieve specific task details |
| POST | `/v1/tasks/{task_uid}/runs` | Execute a task |
| GET | `/v1/tasks/{task_uid}/runs` | List runs for a task |
| GET | `/v1/tasks/{task_uid}/runs/{uid}` | Retrieve run status and results |
| GET | `/v1/feeds` | List custom JSON data feeds |

## Key resources

- **v1** — Operations related to v1
- **v2** — Operations related to v2

## Why Jentic

- **Setup:** Wiring the Roborabbit API by hand means using your workspace API key as a bearer token, sending it on every call to the api.roborabbit.com host, and threading task ids through the runs paths yourself. Through Jentic you install once, import the Roborabbit API from the API Directory, store the API key once, and your agent calls it.
- **Permission scoping:** Roborabbit puts the task id in the URL path (`/v1/tasks/{task_uid}/runs`), so a rule can pin your agent to one task: it can read that task and its runs and nothing else. You choose the operations it may call, so starting a new run is not included unless you add it.
- **Credential handling:** Your Roborabbit API key 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.
- **Discovery method:** Agents search Jentic by intent such as 'list tasks' or 'start a task run', and Jentic returns the matching Roborabbit API operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Greenhouse** — Alternative hr recruiting API
- **Lever** — Alternative hr recruiting API
- **Workday** — Complementary hr recruiting API

## FAQ

### What authentication does the Roborabbit API use?

The Roborabbit API uses a Bearer token in the Authorization header. Through Jentic, these credentials are stored encrypted in your Jentic One instance and injected at execution time, so raw secrets never enter the agent context.

### Can I verify authorization status with the Roborabbit API?

Yes. Use the GET `/v2/auth` endpoint. The API returns structured JSON responses that agents can parse and act on directly.

### What are the rate limits for the Roborabbit API?

Rate limits are not specified in the OpenAPI spec. Check the vendor documentation for current limits. Through Jentic, rate limiting is handled automatically with retry logic built into the execution layer.

### How do I verify authorization status through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'verify authorization status'. Jentic returns the matching Roborabbit API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

### How many endpoints does the Roborabbit API have?

The Roborabbit API exposes 8 endpoints covering v1, v2 operations.

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

Yes. Because you run Jentic One yourself, your own rules decide which Roborabbit operations and credentials the agent may use. Roborabbit puts the task id in the URL path, such as `/v1/tasks/{task_uid}/runs`, so a rule can pin the agent to a single task and let it read only that task and its runs. You pick the operations it may call, so starting a new run with POST `/v1/tasks/{task_uid}/runs` stays off unless you add it.