Install Jentic One Beta

Connect the Piwik PRO Analytics API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Piwik PRO Analytics 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%2Fpiwik.pro%2Fpiwik" | 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%2Fpiwik.pro%2Fpiwik" | 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 Piwik PRO Analytics API.

Create access token

Execute analytics query

Fetch sessions

Use Cases

Patterns agents use Piwik PRO Analytics API for, with concrete tasks.

★ Identity and Authentication Operations

Use the Piwik PRO Analytics API to perform identity auth operations programmatically. The API provides 7 endpoints covering core functionality including create access token, execute analytics query, execute real-time query.

GET STARTED

Start building with Piwik PRO Analytics API

Explore with Jentic One

View OpenAPI Document

Automated Analytics Management

Automate analytics operations by combining multiple Piwik PRO Analytics API endpoints. Agents can execute analytics query and then execute real-time query in a single workflow.

Call POST /api/analytics/v1/query/ to execute analytics query, then verify the result

AI Agent Integration via Jentic

AI agents discover and call Piwik PRO Analytics 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 oauth2 tokens manually.

Search Jentic for 'create access token', load the operation schema, and execute with Jentic-managed credentials

Key Endpoints

7 endpoints — piwik pro analytics api provides programmatic access to query analytics data, sessions, events, real-time data, and manage goals.

METHOD

PATH

DESCRIPTION

POST

/auth/token

Create access token

POST

/api/analytics/v1/query/

Execute analytics query

POST

/api/analytics/v1/real-time-query/

Execute real-time query

POST

/api/analytics/v1/sessions/

Fetch sessions

POST

/api/analytics/v1/events/

Fetch events

POST

/api/analytics/v1/real-time-events/

Fetch real-time events

POST

/api/analytics/v1/manage/goals/

Create a goal

POST

/auth/token

Create access token

POST

/api/analytics/v1/query/

Execute analytics query

POST

/api/analytics/v1/real-time-query/

Execute real-time query

POST

/api/analytics/v1/sessions/

Fetch sessions

POST

/api/analytics/v1/events/

Fetch events

POST

/api/analytics/v1/real-time-events/

Fetch real-time events

POST

/api/analytics/v1/manage/goals/

Create a goal

Why Jentic?

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

Setup

Wiring Piwik PRO Analytics by hand means implementing its OAuth 2.0 token exchange at /auth/token, resolving the per-account host, and handling retries yourself. Through Jentic you install once, import Piwik PRO Analytics from the API Directory, store the credential once, and your agent calls it.

Permission scoping

You limit the agent to the operations it needs, such as running an analytics query or reading real-time events. Because you choose the allowed operations, managing goals stays out of scope unless you add it.

Credential isolation

Your Piwik PRO Analytics OAuth 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 'query analytics sessions' or 'read real-time events', and Jentic returns the matching Piwik PRO Analytics operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

FAQs

Specific to using Piwik PRO Analytics API through Jentic.

What authentication does the Piwik PRO Analytics API use?

The Piwik PRO Analytics API uses OAuth 2.0 for authorization. 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 create access token with the Piwik PRO Analytics API?

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

What are the rate limits for the Piwik PRO Analytics 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 create access token through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'create access token'. Jentic returns the matching Piwik PRO Analytics API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

How many endpoints does the Piwik PRO Analytics API have?

The Piwik PRO Analytics API exposes 7 endpoints covering analytics, auth operations.

Can I limit what my agent is allowed to do with the Piwik PRO Analytics API?

Yes. Jentic One is self-hosted by you, so your own rules decide which Piwik PRO Analytics operations and credentials the agent may use. You can allow it to run an analytics query or read real-time events while keeping other operations, such as creating goals, out of scope until you add them. Because you choose the permitted operations, the agent can only call what you have explicitly enabled.

Piwik PRO Analytics API

Name: Piwik PRO Analytics API
Brand: Piwik PRO Analytics API
Availability: InStock

AI ReadinessAI-Aware (B-)63/100

See full scorecard

Official vendor OpenAPI document · agent-readyIdentity AuthAuthenticationoauth27 EndpointsREST

For Agents

Programmatically create access token, execute analytics query. Covers 7 operations with oauth2 authentication.

Use for: I need to access token, I want to execute analytics query, Search for execute real-time query, Find all fetch sessions

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

Piwik PRO Analytics API provides programmatic access to query analytics data, sessions, events, real-time data, and manage goals. Authentication uses OAuth2 client credentials. The API exposes 7 endpoints secured with oauth2 authentication.

Jentic One on Github View OpenAPI Document

Show dimension breakdown

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: CSignals: 4

92%

Lint Results

Aggregated quality score from linter diagnostics, weighted by severity.

100%

Resolution Completeness

Percentage of `$ref` references that resolve successfully.

Specification Validity

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

35%

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: BSignals: 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

28%

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: ASignals: 1

85%

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: A-Signals: 1

75%

Descriptive Richness

Clarity and depth of descriptions across API elements.

Connect the Piwik PRO Analytics API to your agent

Capabilities

Use Cases

Start building with Piwik PRO Analytics API

Key Endpoints

Why Jentic?

Related APIs

FAQs

Piwik PRO Analytics API

Jentic AI Readiness Score

Piwik PRO Analytics 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