Install Jentic One Beta

Connect the Pilot API to your agent

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

Launch and manage headless Chrome or Firefox browser sessions with custom viewport and user-agent settings

Navigate to URLs, click elements, fill forms, and execute JavaScript in browser context

Extract structured data from web pages using CSS selectors or XPath queries

Capture full-page or element-specific screenshots in PNG or JPEG format

Generate PDFs from web pages with custom formatting and print options

GET STARTED

Start building with Pilot API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use Pilot API for, with concrete tasks.

★ E-commerce Price Monitoring

Monitor competitor pricing across multiple e-commerce platforms by launching browser sessions, navigating to product pages, and extracting price data using CSS selectors. Pilot API handles proxy rotation and anti-bot detection automatically, so the scraper runs reliably without triggering rate limits or IP bans. The extracted data can be stored in a database for trend analysis and alerting.

POST /sessions to create a new browser session, then POST /sessions/{sessionId}/navigate with the target product URL, followed by POST /sessions/{sessionId}/extract using CSS selectors for price elements, and finally DELETE /sessions/{sessionId} to clean up.

Automated Web Testing

Test web applications by simulating user workflows across multiple pages and form submissions. The API exposes click, type, and evaluate endpoints for interacting with page elements, plus screenshot capture for visual regression testing. Session management ensures state is preserved across navigation steps, and console log monitoring helps catch client-side errors during test execution.

Create a session with POST /sessions, navigate to the login page, use POST /sessions/{sessionId}/type to fill credentials, POST /sessions/{sessionId}/click to submit the form, then POST /sessions/{sessionId}/screenshot to capture the result for validation.

Document Generation from Web Content

Generate PDF archives of web pages for compliance, record-keeping, or offline distribution. The /pdf endpoint accepts formatting options like page size, margins, and print backgrounds, and returns a download URL for the generated document. Useful for automating report generation, creating backups of dynamic content, or archiving web-based documentation at a point in time.

POST /sessions with the target URL, wait for page load confirmation, then POST /sessions/{sessionId}/pdf with formatting options to generate the PDF and retrieve the download URL.

Lead Generation and Contact Extraction

Extract contact information, email addresses, and business details from directory websites, search results, or company pages. Pilot API's extraction endpoint accepts multiple selectors and returns structured JSON, making it straightforward to aggregate data across pagination. Proxy rotation ensures the scraper stays under radar, and session reuse across requests improves performance for bulk extraction workflows.

Create a session, navigate to the directory search page, loop through pagination by calling POST /sessions/{sessionId}/click on the next button, and POST /sessions/{sessionId}/extract with selectors for email, phone, and company name on each page iteration.

AI Agent for Web Data Retrieval

Let an AI agent retrieve real-time information from websites by describing the task in natural language, such as 'get the latest blog post from example.com' or 'find the price of this product on retailer.com'. Through Jentic, the agent searches for Pilot API operations by intent, loads the schema for navigation and extraction endpoints, and executes the browser automation workflow without holding raw credentials.

Use the Jentic search query 'extract data from a webpage' to find POST /sessions/{sessionId}/extract, load its schema, then execute with the user-provided URL and CSS selectors.

Key Endpoints

32 endpoints — pilot api is a browser automation and web scraping platform that provides programmatic control over headless chrome and firefox instances.

METHOD

PATH

DESCRIPTION

POST

/sessions

Create a new browser session with specified browser type, viewport, and proxy configuration

POST

/sessions/{sessionId}/navigate

Navigate the browser to a specified URL and wait for page load

POST

/sessions/{sessionId}/click

Click an element on the page identified by CSS selector or XPath

POST

/sessions/{sessionId}/type

Type text into an input field identified by selector

POST

/sessions/{sessionId}/extract

Extract data from the page using CSS selectors or XPath queries

POST

/sessions/{sessionId}/screenshot

Capture a screenshot of the current page or specific element

POST

/sessions/{sessionId}/pdf

Generate a PDF of the current page with custom formatting options

DELETE

/sessions/{sessionId}

Close and delete a browser session to free resources

POST

/sessions

Create a new browser session with specified browser type, viewport, and proxy configuration

POST

/sessions/{sessionId}/navigate

Navigate the browser to a specified URL and wait for page load

POST

/sessions/{sessionId}/click

Click an element on the page identified by CSS selector or XPath

POST

/sessions/{sessionId}/type

Type text into an input field identified by selector

POST

/sessions/{sessionId}/extract

Extract data from the page using CSS selectors or XPath queries

POST

/sessions/{sessionId}/screenshot

Capture a screenshot of the current page or specific element

POST

/sessions/{sessionId}/pdf

Generate a PDF of the current page with custom formatting options

Why Jentic?

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

Setup

Wiring the Pilot API by hand means setting up its bearer auth and coding the full browser session lifecycle, from creating a session through navigate, click, type, extract, and teardown, yourself. Through Jentic you install once, import Pilot from the API Directory, store the bearer token once, and your agent calls it.

Permission scoping

Pilot puts the session id in the URL path (/sessions/{sessionId}/...), so a rule can pin your agent to the sessions it opens: it can navigate, extract, and screenshot within a session. You choose the operations it may call, so ending a session with a delete is not included unless you add it.

Credential isolation

Your Pilot API bearer token 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 'scrape a webpage' or 'take a screenshot of a website', and Jentic returns the matching Pilot browser automation operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

FAQs

Specific to using Pilot API through Jentic.

What authentication does the Pilot API use?

Pilot API uses Bearer token authentication sent in the Authorization header on every request. Tokens are generated from your Pilot API dashboard and can be scoped to specific operations. Through Jentic, tokens are stored encrypted and injected at execution time so they never enter the agent's context.

Can I use the Pilot API to bypass CAPTCHA challenges?

Yes. Pilot API includes built-in CAPTCHA solving for common providers like reCAPTCHA and hCaptcha. When a CAPTCHA is detected during navigation or form submission, it is solved automatically without requiring additional configuration or third-party services.

What are the rate limits for the Pilot API?

Rate limits vary by plan tier. The free tier allows 100 sessions per day with a maximum session duration of 5 minutes. Paid plans offer higher limits and longer session durations. All plans enforce a maximum of 10 concurrent sessions per account to ensure fair resource allocation.

How do I extract data from a dynamic webpage with Pilot API?

Use POST /sessions to create a browser session, navigate to the page with POST /sessions/{sessionId}/navigate, wait for the dynamic content to load (using waitUntil parameters), then call POST /sessions/{sessionId}/extract with CSS selectors or XPath to pull the data. The API handles JavaScript rendering automatically.

Does Pilot API support proxy rotation?

Yes. When creating a session, you can specify proxy rotation settings in the request body. Pilot API will automatically rotate through a pool of residential or datacenter proxies to avoid IP-based rate limiting and detection. You can also bring your own proxy list via the API.

Can I run Pilot API sessions in parallel?

Yes. You can create and manage multiple browser sessions concurrently, up to your account's concurrency limit. Each session is isolated and maintains its own state, cookies, and local storage, making it suitable for parallel scraping or testing workflows.

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

Yes. Because you run Jentic One yourself, your own rules decide which Pilot API operations and credentials the agent may use. Since Pilot puts the session id in the URL path (/sessions/{sessionId}/...), you can pin the agent to the sessions it opens and allow only the calls you choose, such as navigate, extract, and screenshot within a session. Deleting a session is not included unless you add it, so the operator stays in control of teardown and every other operation.

Pilot API

Name: Pilot API
Brand: Pilot API
Availability: InStock

Developer ToolsTesting Qabearer32 EndpointsREST

For Agents

Automate browser interactions, scrape web content, capture screenshots, generate PDFs, and extract structured data from websites through a managed headless browser API.

Use for: I need to scrape product prices from an e-commerce website, Take a screenshot of a webpage and save it to cloud storage, Fill out a form on a website and submit it programmatically, Generate a PDF of a web page for archival purposes

Not supported: Does not handle server-side rendering, static site generation, or website hosting - use for browser automation, web scraping, and data extraction from existing websites only.

Pilot API is a browser automation and web scraping platform that provides programmatic control over headless Chrome and Firefox instances. The API exposes endpoints for session management, page navigation, element interaction, screenshot capture, PDF generation, and data extraction. Built for developers who need reliable browser automation without managing infrastructure, Pilot API handles proxy rotation, CAPTCHA solving, and anti-bot detection automatically. Authentication is via Bearer token, and sessions are stateful with configurable timeouts. Through Jentic, AI agents can discover and execute browser automation tasks by intent, with credentials managed securely in the encrypted vault.

Jentic One on Github View OpenAPI Document

Connect the Pilot API to your agent

Capabilities

Start building with Pilot API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

Pilot API