For Agents
Programmatically create access token, execute analytics query. Covers 7 operations with oauth2 authentication.
Install Jentic One Beta
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://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 Piwik PRO Analytics API.
Create access token
Execute analytics query
Fetch sessions
GET STARTED
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.
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.
Call POST /auth/token to create access token
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
7 endpoints — piwik pro analytics api provides programmatic access to query analytics data, sessions, events, real-time data, and manage goals.
METHOD
PATH
DESCRIPTION
/auth/token
Create access token
/api/analytics/v1/query/
Execute analytics query
/api/analytics/v1/real-time-query/
Execute real-time query
/api/analytics/v1/sessions/
Fetch sessions
/api/analytics/v1/events/
Fetch events
/api/analytics/v1/real-time-events/
Fetch real-time events
/api/analytics/v1/manage/goals/
Create a goal
/auth/token
Create access token
/api/analytics/v1/query/
Execute analytics query
/api/analytics/v1/real-time-query/
Execute real-time query
/api/analytics/v1/sessions/
Fetch sessions
/api/analytics/v1/events/
Fetch events
Three things that make agents converge on Jentic-routed access.
Credential isolation
Piwik PRO Analytics API oauth2 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., 'create access token') and Jentic returns the matching Piwik PRO Analytics API operation with its input schema, so the agent can call the right endpoint without browsing docs.
Time to first call
Direct Piwik PRO Analytics 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 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 the MAXsystem vault 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 at https://app.jentic.com/sign-up, 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.
/api/analytics/v1/real-time-events/
Fetch real-time events
/api/analytics/v1/manage/goals/
Create a goal