Install Jentic One Beta
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Smartlook 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%2Fsmartlookcom%2Fsmartlookcom" | shStep 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%2Fsmartlookcom%2Fsmartlookcom" | 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 Smartlook API.
Search sessions
Get session details
Delete visitor
Query and filter Smartlook API records by parameters
Monitor Smartlook API operational status and events
GET STARTED
Patterns agents use Smartlook API for, with concrete tasks.
★ Identity and Authentication Operations
Use the Smartlook API to perform identity auth operations programmatically. The API provides 23 endpoints covering core functionality including search sessions, get session details, get session public link.
Call POST /api/v1/sessions to search sessions
Automated sessions Management
Automate sessions operations by combining multiple Smartlook API endpoints. Agents can get session details and then get session public link in a single workflow.
Call GET /api/v1/sessions/{id} to get session details, then verify the result
AI Agent Integration via Jentic
AI agents discover and call Smartlook 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 'search sessions', load the operation schema, and execute with Jentic-managed credentials
23 endpoints — smartlook rest api for managing sessions, visitors, events, funnels, and webhooks.
METHOD
PATH
DESCRIPTION
/api/v1/sessions
Search sessions
/api/v1/sessions/{id}
Get session details
/api/v1/sessions/{id}/public
Get session public link
/api/v1/visitors/{id}
Get visitor details
/api/v1/visitors/{id}
Delete visitor
/api/v1/visitors/{id}/sessions
Get visitor sessions
/api/v1/visitors/{id}/events
Get visitor events
/api/v1/visitors/search
Search visitors
/api/v1/sessions
Search sessions
/api/v1/sessions/{id}
Get session details
/api/v1/sessions/{id}/public
Get session public link
/api/v1/visitors/{id}
Get visitor details
/api/v1/visitors/{id}
Delete visitor
/api/v1/visitors/{id}/sessions
Get visitor sessions
/api/v1/visitors/{id}/events
Get visitor events
/api/v1/visitors/search
Search visitors
What agents get from Jentic-routed access to this vendor.
Setup
Wiring Smartlook by hand means handling its bearer auth, resolving the right region host (api.{region}.smartlook.cloud, defaulting to eu), and managing retries yourself. Through Jentic you install once, import the Smartlook API from the API Directory, store the token once, and your agent calls it.
Permission scoping
Smartlook puts the visitor and session id in the URL path (/api/v1/visitors/{id}, /api/v1/sessions/{id}), so a rule can pin your agent to one visitor: it can read that visitor's sessions and events. You choose the operations it may call, so deleting a visitor is not included unless you add it.
Credential isolation
Your Smartlook 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 'find a visitor's sessions' or 'search recorded sessions', and Jentic returns the matching Smartlook operation with its input schema so the agent calls the right endpoint without browsing the reference docs.
Alternatives and complements available in the Jentic catalogue.
Specific to using Smartlook API through Jentic.
What authentication does the Smartlook API use?
The Smartlook 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 search sessions with the Smartlook API?
Yes. Use the POST /api/v1/sessions endpoint. The API returns structured JSON responses that agents can parse and act on directly.
What are the rate limits for the Smartlook 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 sessions through Jentic?
Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'search sessions'. Jentic returns the matching Smartlook API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.
How many endpoints does the Smartlook API have?
The Smartlook API exposes 23 endpoints covering sessions, visitors, events operations.
Can I limit what my agent is allowed to do with the Smartlook API?
Yes. Because you run Jentic One yourself, your own rules decide which Smartlook operations and credentials the agent may use, and Smartlook puts the visitor and session id in the URL path (/api/v1/visitors/{id}, /api/v1/sessions/{id}), so you can pin the agent to a single visitor and let it read only that visitor's sessions and events. You pick the operations it can call, so a destructive call like DELETE /api/v1/visitors/{id} stays off limits unless you explicitly grant it. The stored bearer token is injected only when an allowed operation runs, so the agent never sees the raw secret or reaches endpoints you have not approved.
Know of an official OpenAPI document? Contribute it →
For Agents
Programmatically search sessions, get session details. Covers 23 operations with bearer authentication.
Use for: I need to sessions, I want to session details, Search for session public link, Find all visitor details
Not supported: Does not handle payments, communications, or crm - use for identity and authentication only.
Smartlook REST API for managing sessions, visitors, events, funnels, and webhooks. Rate limits: Free plan 20 req/hr, Paid plans 100 req/hr, REST API add-on 1,000 req/hr. Inactive tokens expire after 90 days. The API exposes 23 endpoints secured with bearer authentication.