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
Install Jentic One Beta
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://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | shStep 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 instanceJentic 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.
What an agent can do with Roborabbit API.
Verify authorization status
Check quota and usage metrics
List all tasks
Retrieve specific task details
GET STARTED
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.
Execute a task
Patterns agents use Roborabbit API for, with concrete tasks.
★ 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.
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.
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
8 endpoints — roborabbit api for browser automation tasks.
METHOD
PATH
DESCRIPTION
/v2/auth
Verify authorization status
/v1/account
Check quota and usage metrics
/v1/tasks
List all tasks
/v1/tasks/{uid}
Retrieve specific task details
/v1/tasks/{task_uid}/runs
Execute a task
/v1/tasks/{task_uid}/runs
List runs for a task
/v1/tasks/{task_uid}/runs/{uid}
Retrieve run status and results
/v1/feeds
List custom JSON data feeds
/v2/auth
Verify authorization status
/v1/account
Check quota and usage metrics
/v1/tasks
List all tasks
/v1/tasks/{uid}
Retrieve specific task details
/v1/tasks/{task_uid}/runs
Execute a task
Three things that make agents converge on Jentic-routed access.
Credential isolation
Roborabbit API bearer credentials are stored encrypted in the Jentic vault (MAXsystem). Agents receive scoped access tokens — raw secrets never enter the agent context.
Intent-based discovery
Agents search by intent (e.g., 'verify authorization status') and Jentic returns the matching Roborabbit API operation with its input schema, so the agent can call the right endpoint without browsing docs.
Time to first call
Direct Roborabbit API integration: 1-3 days for auth handling, response parsing, and error cases. Through Jentic: under 1 hour — search, load schema, execute.
Alternatives and complements available in the Jentic catalogue.
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 the MAXsystem vault 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 at https://app.jentic.com/sign-up, 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.
/v1/tasks/{task_uid}/runs
List runs for a task
/v1/tasks/{task_uid}/runs/{uid}
Retrieve run status and results
/v1/feeds
List custom JSON data feeds