Install Jentic One Beta

Connect the Screenpipe API to your agent

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

Search screen and audio content

Keyword search

Server health check

List audio devices

Start audio recording

GET STARTED

Start building with Screenpipe API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use Screenpipe API for, with concrete tasks.

★ HR and Recruiting Operations

Use the Screenpipe API to perform hr recruiting operations programmatically. The API provides 13 endpoints covering core functionality including search screen and audio content, keyword search, server health check.

Call GET /search to search screen and audio content

Automated Audio Management

Automate audio operations by combining multiple Screenpipe API endpoints. Agents can keyword search and then server health check in a single workflow.

Call GET /search/keyword to keyword search, then verify the result

AI Agent Integration via Jentic

AI agents discover and call Screenpipe 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 none tokens manually.

Search Jentic for 'search screen and audio content', load the operation schema, and execute with Jentic-managed credentials

Key Endpoints

13 endpoints — screenpipe local rest api for searching and managing screen and audio recordings.

METHOD

PATH

DESCRIPTION

GET

/search

Search screen and audio content

GET

/search/keyword

Keyword search

GET

/health

Server health check

GET

/audio/list

List audio devices

POST

/audio/start

Start audio recording

POST

/audio/stop

Stop audio recording

GET

/vision/list

List monitors

GET

/frames/{id}

Get frame data

GET

/search

Search screen and audio content

GET

/search/keyword

Keyword search

GET

/health

Server health check

GET

/audio/list

List audio devices

POST

/audio/start

Start audio recording

POST

/audio/stop

Stop audio recording

GET

/vision/list

List monitors

GET

/frames/{id}

Get frame data

Why Jentic?

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

Setup

Wiring the Screenpipe API by hand means standing up its request layer against screenpi.pe, coordinating the audio and vision capture calls, and building your own retry handling. Through Jentic you install once, import Screenpipe from the API Directory, store its credential once, and your agent calls it.

Permission scoping

Screenpipe exposes search, audio, vision, and frame operations, so you limit the agent to the operations it needs, such as searching screen and audio content or listing audio. You choose the operations it may call, so starting or stopping audio capture is not included unless you add it.

Credential isolation

Your Screenpipe credential 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 'search screen and audio content' or 'list captured audio', and Jentic returns the matching Screenpipe operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

FAQs

Specific to using Screenpipe API through Jentic.

What authentication does the Screenpipe API use?

The Screenpipe API uses no authentication. 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 search screen and audio content with the Screenpipe API?

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

What are the rate limits for the Screenpipe 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 search screen and audio content through Jentic?

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

How many endpoints does the Screenpipe API have?

The Screenpipe API exposes 13 endpoints covering audio, frames, search operations.

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

Yes. The Screenpipe API exposes search, audio, vision, and frame operations, and because Jentic One is self-hosted, your own rules decide which of those the agent may call. You can allow it to search screen and audio content or list audio devices while withholding operations like starting or stopping audio recording. The agent can only invoke the operations and credentials you have granted it.

Screenpipe API

Name: Screenpipe API
Brand: Screenpipe API
Availability: InStock

Official vendor OpenAPI document · agent-readyHR recruitingEmployee Managementnone13 EndpointsREST

For Agents

Programmatically search screen and audio content, keyword search. Covers 13 operations.

Use for: I need to screen and audio content, I want to keyword search, Search for server health check, Find all audio devices

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

Screenpipe local REST API for searching and managing screen and audio recordings. Screenpipe is an AI-powered screen and audio memory tool that records, indexes, and allows searching of everything displayed on screen or heard through audio. The API exposes 13 endpoints.

Jentic One on Github View OpenAPI Document

Connect the Screenpipe API to your agent

Capabilities

Start building with Screenpipe API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

Screenpipe API