Install Jentic One Beta

Connect the Slickstream Engagement API to your agent

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://jentic.com/install.sh?src=apis&api=%2Fapis%2Fslickstream.com%2Fslickstream" | 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%2Fslickstream.com%2Fslickstream" | 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 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

Monitor Slickstream Engagement API operational status and events

GET STARTED

Start building with Slickstream Engagement API

Explore with Jentic One

View OpenAPI Document

Use Cases

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

Key Endpoints

2 endpoints — api for retrieving site summary data and content analytics from slickstream engagement suite.

METHOD

PATH

DESCRIPTION

GET

/example/{siteCode}/v1/site

Get site summary data

GET

/example/{siteCode}/v1/site-content-analytics

Get content analytics

GET

/example/{siteCode}/v1/site

Get site summary data

GET

/example/{siteCode}/v1/site-content-analytics

Get content analytics

Why Jentic?

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

Setup

Wiring the Slickstream Engagement API by hand means passing your apiKey as a query parameter to api.slickstream.com and handling the site and content analytics reads yourself. Through Jentic you install once, import Slickstream from the API Directory, store the API key once, and your agent calls it.

Permission scoping

Slickstream puts the site code in the URL path (/example/{siteCode}/v1/site), so a rule can pin your agent to one site. You choose the operations it may call, so if you only grant the site read, the content analytics read is not included unless you add it.

Credential isolation

Your Slickstream API key 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 'get site details' or 'read content analytics for a site', and Jentic returns the matching Slickstream operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

FAQs

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 your Jentic One instance 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 through Jentic One, the self-hosted execution layer, 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.

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

Yes. Because you run Jentic One yourself, your own rules decide which Slickstream operations and credentials the agent may use. Slickstream puts the site code in the URL path, such as /example/{siteCode}/v1/site, so a rule can pin the agent to a single site. You also choose the operations it may call, so granting the site summary read (GET /example/{siteCode}/v1/site) does not include the content analytics read (GET /example/{siteCode}/v1/site-content-analytics) unless you add it.

Slickstream Engagement API

Name: Slickstream Engagement API
Brand: Slickstream Engagement API
Availability: InStock

AI ReadinessFoundational (D+)47/100

See full scorecard

Official vendor OpenAPI document · agent-readyAnalyticsData PipelinesapiKey2 EndpointsREST

For Agents

Programmatically get site summary data, get content analytics. Covers 2 operations with apiKey authentication.

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.

Jentic One on Github View OpenAPI Document

Show dimension breakdown

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: A+Signals: 4

99%

Lint Results

Aggregated quality score from linter diagnostics, weighted by severity.

100%

Resolution Completeness

Percentage of `$ref` references that resolve successfully.

100%

Specification Validity

Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).

75%

Structural Integrity

Structural correctness score based on schema issues using logarithmic dampening.

Developer Experience & Jentic Compatibility

Clarity, completeness, and ingestion readiness for developers and tooling.

Grade: B-Signals: 4

Example Density

How richly the API is illustrated with examples.

100%

Example Validity

Percentage of examples that conform to their schemas.

50%

Response Coverage

Percentage of operations with complete response definitions (success, client error, server error).

100%

Tooling Readiness

Health of API ingestion, bundling, and resolution within Jentic pipelines.

AI-Readiness & Agent Experience

Semantic breadth, depth, and agent comprehension for AI systems.

Grade: DSignals: 4

26%

Description Coverage

Coverage of descriptions across API elements.

Error Standardization

Coverage of RFC 9457 Problem Details for error responses.

100%

OperationId Quality

Coverage, uniqueness, and casing consistency of operationIds for AI inference.

50%

Summary Coverage

Coverage of summaries across operations/tags/info.

Agent Usability

Functional utility, complexity comfort, and AI orchestration readiness.

Grade: A+Signals: 1

94%

Complexity Comfort

Agent comfort level based on API operational and structural complexity.

Security

Trust, risk posture, and security compliance.

Grade: FSignals: 1

15%

Authentication Strength

Average quality of security schemes based on authentication method strength (weakest link for OAuth2).

100

AI Discoverability

Findability, semantic richness, and reasoning readiness.

Grade: A+Signals: 1

100%

Descriptive Richness

Clarity and depth of descriptions across API elements.

Connect the Slickstream Engagement API to your agent

Capabilities

Start building with Slickstream Engagement API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

Slickstream Engagement API

Jentic AI Readiness Score

Slickstream Engagement API

Foundational Compliance

Lint Results

Resolution Completeness

Specification Validity

Structural Integrity

Developer Experience & Jentic Compatibility

Example Density

Example Validity

Response Coverage

Tooling Readiness

AI-Readiness & Agent Experience

Description Coverage

Error Standardization

OperationId Quality

Summary Coverage

Agent Usability

Complexity Comfort

Security

Authentication Strength

AI Discoverability

Descriptive Richness