Install Jentic One Beta

Connect the Roborabbit API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Roborabbit 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%2Froborabbit.com%2Froborabbit" | 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%2Froborabbit.com%2Froborabbit" | 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 Roborabbit API.

Verify authorization status

Check quota and usage metrics

List all tasks

Retrieve specific task details

Execute a task

Use Cases

GET STARTED

Start building with Roborabbit API

Explore with Jentic One

View OpenAPI Document

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.

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.

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

Key Endpoints

8 endpoints — roborabbit api for browser automation tasks.

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

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

Why Jentic?

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

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 isolation

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.

Intent-based discovery

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.

FAQs

Specific to using Roborabbit API through Jentic.

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.

Roborabbit API

AI ReadinessAI-Aware (B)66/100

See full scorecard

Official vendor OpenAPI document · agent-readyHR recruitingRecruiting Atsbearer8 EndpointsREST

For Agents

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

Use for: I need to verify authorization status, I want to check quota and usage metrics, Search for all tasks, Find all specific task details

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

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.

Jentic One on Github View OpenAPI Document

Show dimension breakdown

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: ASignals: 4

99%

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).

35%

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: B-Signals: 4

Example Density

How richly the API is illustrated with examples.

100%

Example Validity

Percentage of examples that conform to their schemas.

50%

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: C-Signals: 4

54%

Description Coverage

Coverage of descriptions across API elements.

Error Standardization

Coverage of RFC 9457 Problem Details for error responses.

100%

OperationId Quality

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

53%

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: B-Signals: 1

60%

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: B+Signals: 1

67%

Descriptive Richness

Clarity and depth of descriptions across API elements.

Connect the Roborabbit API to your agent

Capabilities

Use Cases

Start building with Roborabbit API

Key Endpoints

Why Jentic?

Related APIs

FAQs

Roborabbit API

Jentic AI Readiness Score

Roborabbit 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