Flowsery Analytics Public API
68
AI ReadinessAI-Aware (B+)68/100
Official vendor OpenAPI document · agent-readyAnalyticsWeb Analyticsbearer28 EndpointsREST
For Agents
Read web analytics for a website and record conversion events: traffic, revenue, and engagement by date range, dimension breakdowns, realtime counts, single-visitor timelines, and goal and payment recording.
Use for: Get headline traffic metrics for last month, Break down visitors by acquisition channel, Show the visitors active right now, Record a goal completion from my backend
Not supported: Does not handle ad campaign management, tag deployment, or session recording. Use for reading web analytics and recording conversion events only.
The Flowsery Analytics Public API reads web analytics and records conversion events for a website. It returns traffic, revenue, and engagement for any date range and breaks visitors down by page, referrer, channel, campaign, country, device, browser, or operating system, and it can pull a single visitor's full activity timeline. It counts the visitors active right now and maps their locations, records goals and payments from your own backend, and lists AI-detected issues so a team can act on anomalies in the data.
Install Jentic One Beta
Connect the Flowsery Analytics Public API to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Flowsery Analytics Public 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.
1
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%2Fflowsery.com%2Fflowsery" | sh2
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%2Fflowsery.com%2Fflowsery" | 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.
Capabilities
What an agent can do with Flowsery Analytics Public API.
Read headline traffic, revenue, and engagement metrics for a date range
Break visitors down by page, referrer, channel, campaign, country, device, browser, or OS
Pull metrics bucketed over time as a time series
Count the visitors active right now and map their locations
Record a goal completion or a payment from your own backend
Read a single visitor's full activity timeline
List AI-detected issues and update their status
Use Cases
Patterns agents use Flowsery Analytics Public API for, with concrete tasks.
★ Agent analytics reporting
An AI agent connected through Jentic answers a question about a site's performance by reading the headline metrics for a date range and breaking visitors down by channel or page, so a stakeholder gets a live answer without the developer wiring the bearer auth or paging each breakdown by hand.
Read headline metrics for last month and break visitors down by acquisition channel for a summary
Server-side conversion tracking
A backend records goals and payments directly through the events endpoints when a sale or renewal happens, so revenue and conversions are measured from the source of truth rather than a browser tag, and a refund can be recorded or a mis-fired goal deleted.
Record a payment and a goal completion from the backend and delete a goal that fired in error
Realtime monitoring and issue triage
An operations assistant counts the visitors active right now and reviews the AI-detected issues, updating an issue's status as it is handled, so a spike or an anomaly is caught and tracked from live data instead of a next-day report.
Count active visitors, open the current AI-detected issues, and update one issue's status to in progress
Key Endpoints
28 endpoints — the flowsery analytics public api reads web analytics and records conversion events for a website.
METHOD
PATH
DESCRIPTION
GET
/overview
Headline metrics for a date range
GET
/timeseries
Metrics bucketed over time
GET
/pages
Break down visitors by page path
GET
/breakdown
Break down visitors by any supported dimension
GET
/realtime
Count visitors active right now
POST
/goals
Record a goal completion
POST
/payments
Record a payment, renewal, or refund
GET
/visitors/{visitorId}
A visitor's profile and activity timeline
GET
/overview
Headline metrics for a date range
GET
/timeseries
Metrics bucketed over time
GET
/pages
Break down visitors by page path
GET
/breakdown
Break down visitors by any supported dimension
GET
/realtime
Count visitors active right now
POST
/goals
Record a goal completion
POST
/payments
Record a payment, renewal, or refund
GET
/visitors/{visitorId}
A visitor's profile and activity timeline
Jentic AI Readiness Score
This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use.
F
Flowsery Analytics Public API
- AI-Aware (B+)68/100
99
Foundational Compliance63
Developer Experience & Jentic Compatibility49
AI-Readiness & Agent Experience94
Agent Usability60
Security81
AI DiscoverabilityPowered by JenticScoring Framework 1.0.0 | Scoring Engine 0.4.2
Show dimension breakdown
99
Foundational Compliance
Base layer of spec validity and structural soundness.
Grade: A+Signals: 4
95%
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).
100%
Structural Integrity
Structural correctness score based on schema issues using logarithmic dampening.
63
Developer Experience & Jentic Compatibility
Clarity, completeness, and ingestion readiness for developers and tooling.
Grade: B-Signals: 4
0%
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.
49
AI-Readiness & Agent Experience
Semantic breadth, depth, and agent comprehension for AI systems.
Grade: D+Signals: 4
43%
Description Coverage
Coverage of descriptions across API elements.
0%
Error Standardization
Coverage of RFC 9457 Problem Details for error responses.
100%
OperationId Quality
Coverage, uniqueness, and casing consistency of operationIds for AI inference.
54%
Summary Coverage
Coverage of summaries across operations/tags/info.
94
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.
60
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).
81
AI Discoverability
Findability, semantic richness, and reasoning readiness.
Grade: ASignals: 1
81%
Descriptive Richness
Clarity and depth of descriptions across API elements.
Score it yourself
Every API in the directory is allowlisted, so you can re-score it with no key required.
npx @jentic/api-scorecard-cli score <openapi-url>Why Jentic?
What agents get from Jentic-routed access to this vendor.
Setup
Wiring Flowsery by hand means handling its bearer auth, choosing between a website key and a workspace token, and passing the right website selector on each call yourself. Through Jentic you install once, import Flowsery from the API Directory, store the token once, and your agent calls it.
Permission scoping
Flowsery takes the website selector as a parameter, not a path segment, so rules bound which operations your agent may call, not which website. Limit it to the read operations, such as metrics and breakdowns, so recording and deleting goals and payments stay out of reach unless you add those operations.
Credential isolation
Your Flowsery 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 'get web analytics for a date range' or 'break down visitors by channel', and Jentic returns the matching Flowsery operation with its input schema so the agent calls the right endpoint without reading the reference docs.
Related APIs
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using Flowsery Analytics Public API through Jentic.
What authentication does the Flowsery Analytics API use?
The Flowsery Analytics API authenticates with a bearer token in the Authorization header, per its OpenAPI spec: a website API key scoped to one website, or a workspace token that spans every website in the account. Through Jentic the token is stored encrypted by your own Jentic One instance and injected at call time, so it never lands in the agent's context.
Is there a Flowsery MCP server?
You don't need an MCP server to give your agent Flowsery. Jentic connects it directly from the API Directory: import it, store your credential once, and your agent calls the metrics, breakdown, and event operations on demand, without a separate server's tool definitions loaded into its context.
Can I limit what my agent is allowed to do with the Flowsery Analytics API?
Yes. Flowsery takes the website selector as a parameter rather than a path segment, so a rule bounds which operations the agent may call. Allow only the read operations, such as reading metrics and breakdowns, so the agent can report analytics but cannot record or delete goals and payments, with every call logged.
Can I record conversions from my backend with the Flowsery Analytics API?
Yes. The goals endpoint records a goal completion and the payments endpoint records a payment, renewal, or refund from your own backend, and matching delete operations remove entries recorded in error.
What are the rate limits for the Flowsery Analytics API?
The OpenAPI spec does not specify rate limits. Check the vendor documentation at https://flowsery.com for current limits before pulling large date ranges or many breakdowns.
How do I read a site's metrics through Jentic?
Search Jentic for 'get web analytics for a date range', which returns the Flowsery overview operation with its input schema, then pass the date range and read the headline metrics back. To run it on your own infrastructure, install Jentic One from its GitHub repo.
GET STARTED