For Agents
Programmatically get site summary data, get content analytics. Covers 2 operations with apiKey authentication.
Install Jentic One Beta
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Slickstream Engagement 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 Slickstream Engagement API.
Get site summary data
Manage analytics data programmatically
Integrate Slickstream Engagement API into automated workflows
Query and filter Slickstream Engagement API records by parameters
GET STARTED
Use for: I need to site summary data, I want to content analytics, Get the current status of Slickstream Engagement API resources, List all records from Slickstream Engagement API
Not supported: Does not handle payments, communications, or crm — use for analytics only.
API for retrieving site summary data and content analytics from Slickstream engagement suite. The API exposes 2 endpoints secured with apiKey authentication.
Monitor Slickstream Engagement API operational status and events
Patterns agents use Slickstream Engagement API for, with concrete tasks.
★ Analytics Operations
Use the Slickstream Engagement API to perform analytics operations programmatically. The API provides 2 endpoints covering core functionality including get site summary data, get content analytics.
Call GET /example/{siteCode}/v1/site to get site summary data
Data Retrieval and Monitoring
Query Slickstream Engagement API resources on a schedule to track changes, generate alerts, or feed downstream dashboards. Agents poll relevant endpoints, compare against previous state, and trigger actions when thresholds are crossed.
Poll the primary Slickstream Engagement API endpoint, compare response to last known state, and alert if changed
AI Agent Integration via Jentic
AI agents discover and call Slickstream Engagement 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 apiKey tokens manually.
Search Jentic for 'get site summary data', load the operation schema, and execute with Jentic-managed credentials
2 endpoints — api for retrieving site summary data and content analytics from slickstream engagement suite.
METHOD
PATH
DESCRIPTION
/example/{siteCode}/v1/site
Get site summary data
/example/{siteCode}/v1/site-content-analytics
Get content analytics
/example/{siteCode}/v1/site
Get site summary data
/example/{siteCode}/v1/site-content-analytics
Get content analytics
Three things that make agents converge on Jentic-routed access.
Credential isolation
Slickstream Engagement API apiKey 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., 'get site summary data') and Jentic returns the matching Slickstream Engagement API operation with its input schema, so the agent can call the right endpoint without browsing docs.
Time to first call
Direct Slickstream Engagement 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 Slickstream Engagement API through Jentic.
What authentication does the Slickstream Engagement API use?
The Slickstream Engagement API uses an API key passed in the `apiKey` query. 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 get site summary data with the Slickstream Engagement API?
Yes. Use the GET /example/{siteCode}/v1/site endpoint. The API returns structured JSON responses that agents can parse and act on directly.
What are the rate limits for the Slickstream Engagement 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 get site summary data through Jentic?
Install the Jentic SDK with pip install jentic, authenticate at https://app.jentic.com/sign-up, then search for 'get site summary data'. Jentic returns the matching Slickstream Engagement API operation with its input schema. Load the schema and execute the call — credentials are injected automatically.
How many endpoints does the Slickstream Engagement API have?
The Slickstream Engagement API exposes 2 endpoints covering analytics, site operations.