Install Jentic One Beta

Connect the Hoot Lens API to your agent

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

List the sites you track and read each site's install status

Read session recordings and the narrative of a page view or visit

Pull heatmap cohorts and their sampled clicks for a site

Read visits, traffic, weekly trends, and weekly summaries

Define goals and funnels and read their conversion statistics

GET STARTED

Start building with Hoot Lens API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use Hoot Lens API for, with concrete tasks.

★ On-Site Behavior Evidence Review

Review what visitors actually did on a site using recordings and plain-language narratives rather than raw event logs. The API lists visits for a site and returns a narrative of a specific visit or page view. Product teams use this to understand friction on a page from observed behavior, not guesswork.

GET /v1/projects/{projectId}/sessions to list visits, then GET /v1/projects/{projectId}/sessions/{sessionId}/narrative to read what happened in one visit.

Goal and Funnel Conversion Tracking

Measure how visitors convert by defining goals and funnels and reading their statistics, instead of stitching events together manually. The API creates a goal or funnel for a site and returns its conversion statistics. Growth teams use this to monitor conversion on key flows.

POST /v1/projects/{projectId}/goals to define a goal, then GET /v1/projects/{projectId}/goals/stats to read its conversion statistics.

Change Impact Measurement

Tie a product change to its effect by logging a change marker and reading the impact Hoot Lens measures against it. The API records a change on a site and returns the measured impact of that change. Teams use this to confirm whether a release helped or hurt key behavior.

POST /v1/projects/{projectId}/changes to log a release, then GET /v1/projects/{projectId}/changes/{changeId}/impact to read its measured effect.

Agent-Driven Analytics Readout

An AI agent produces a weekly on-site readout without a custom analytics client. Through Jentic the agent discovers the traffic and trend operations, loads their schemas, and calls them for a site, then summarizes what changed. This lets a reporting assistant answer behavior questions directly from the evidence.

Search Jentic for 'read site analytics', call GET /v1/projects/{projectId}/traffic and GET /v1/projects/{projectId}/trends, and summarise the week's traffic and trend changes.

Key Endpoints

53 endpoints — the hoot lens api records website interaction evidence for the sites you add and returns it as visits, recordings, heatmaps, goals, funnels, and change impact.

METHOD

PATH

DESCRIPTION

GET

/v1/projects

List tracked sites

GET

/v1/projects/{projectId}/recordings

List session recordings for a site

GET

/v1/projects/{projectId}/sessions

List visits for a site

GET

/v1/projects/{projectId}/heatmaps

List heatmap cohorts for a site

GET

/v1/projects/{projectId}/goals

List goals for a site

POST

/v1/projects/{projectId}/goals

Create a goal for a site

GET

/v1/projects/{projectId}/funnels

List funnels for a site

POST

/v1/projects/{projectId}/changes

Log a change marker

GET

/v1/projects

List tracked sites

GET

/v1/projects/{projectId}/recordings

List session recordings for a site

GET

/v1/projects/{projectId}/sessions

List visits for a site

GET

/v1/projects/{projectId}/heatmaps

List heatmap cohorts for a site

GET

/v1/projects/{projectId}/goals

List goals for a site

POST

/v1/projects/{projectId}/goals

Create a goal for a site

GET

/v1/projects/{projectId}/funnels

List funnels for a site

POST

/v1/projects/{projectId}/changes

Log a change marker

Why Jentic?

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

Setup

Wiring Hoot Lens by hand means handling its bearer auth, whether a Firebase token or a personal access token, and paging a site's evidence yourself. Through Jentic you install once, import Hoot Lens from the API Directory, store the credential once, and your agent calls the read endpoints.

Permission scoping

Hoot Lens puts the site id in the URL path (/v1/projects/{projectId}/...), so a rule can pin your agent to one site. You choose the operations it may call, so write operations like deleting a goal or rotating a webhook secret are not included unless you add them.

Credential isolation

Your Hoot Lens 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 'read site analytics' or 'list session recordings', and Jentic returns the matching Hoot Lens operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

FAQs

Specific to using Hoot Lens API through Jentic.

Is there a Hoot Lens MCP server?

You do not need an MCP server to give your agent the Hoot Lens API. Jentic connects it directly from the API Directory: import Hoot Lens, store your token once, and your agent calls the recording, heatmap, and funnel endpoints. Operations are discovered on demand, so no extra server's tool definitions load into the agent's context.

What authentication does the Hoot Lens API use?

The Hoot Lens API authenticates with a bearer token in the Authorization header, per its OpenAPI spec, and that credential is either a Firebase ID token for a signed-in person or a personal access token. Through Jentic the token is stored encrypted by your own Jentic One instance and injected at call time, so it never enters the agent's prompt or logs.

Can I read session recordings and heatmaps with the Hoot Lens API?

Yes. GET /v1/projects/{projectId}/recordings lists recordings, GET /v1/projects/{projectId}/sessions/{sessionId}/narrative returns a plain-language narrative of a visit, and GET /v1/projects/{projectId}/heatmaps lists heatmap cohorts with sampled clicks. Everything returned is observed behavior with its evidence.

What are the rate limits for the Hoot Lens API?

The OpenAPI spec does not specify numeric rate limits for the Hoot Lens API. Check the Hoot Lens documentation at https://hootlens.com for the current limits that apply to your account.

How do I read site analytics through Jentic?

Search Jentic with the query 'read site analytics', load the schema for GET /v1/projects/{projectId}/traffic, and execute it for your site, then read GET /v1/projects/{projectId}/trends. To run it on your own infrastructure, install Jentic One from its GitHub repo.

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

Yes. Write a rule that allows only the read operations under one project id, such as GET /v1/projects/{projectId}/sessions and GET /v1/projects/{projectId}/heatmaps, so the agent can read evidence for that one site and cannot change its goals, funnels, or webhooks, and every call it makes is logged.

Hoot Lens API

AI ReadinessAI-Aware (B)65/100

See full scorecard

Official vendor OpenAPI document · agent-readyAnalyticsWeb Analyticsbearer53 EndpointsREST

For Agents

Read website behavior evidence for your sites: visits, session recordings, heatmaps, traffic trends, goals, funnels, and the measured impact of changes you log.

Use for: List the sites tracked in Hoot Lens, Read the session recordings for a site, Get the heatmap for a page and its sampled clicks, Create a conversion goal for a site

Not supported: Does not run A/B test variants, serve ads, or manage a tag container. Use for reading on-site behavior evidence such as visits, recordings, heatmaps, goals, and funnels only.

The Hoot Lens API records website interaction evidence for the sites you add and returns it as visits, recordings, heatmaps, goals, funnels, and change impact. It reads session recordings and their narratives, heatmap cohorts and sampled clicks, traffic and weekly trends, and the measured impact of the changes you log. Use it to read observed on-site behavior and tie product changes to their effect, from an app or an agent.

Jentic One on Github View OpenAPI Document

Show dimension breakdown

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: A-Signals: 4

96%

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).

17%

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: D+Signals: 4

40%

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.

57%

Summary Coverage

Coverage of summaries across operations/tags/info.

Agent Usability

Functional utility, complexity comfort, and AI orchestration readiness.

Grade: A+Signals: 1

93%

Complexity Comfort

Agent comfort level based on API operational and structural complexity.

Security

Trust, risk posture, and security compliance.

Grade: B-Signals: 1

60%

Authentication Strength

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

AI Discoverability

Findability, semantic richness, and reasoning readiness.

Grade: B+Signals: 1

69%

Descriptive Richness

Clarity and depth of descriptions across API elements.

Connect the Hoot Lens API to your agent

Capabilities

Start building with Hoot Lens API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

Hoot Lens API

Jentic AI Readiness Score

Hoot Lens 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