Install Jentic One Beta
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Roark 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%2Froark.ai%2Froark" | shStep 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%2Froark.ai%2Froark" | 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 Roark Analytics API.
Start a simulation against a voice or chat agent from a built-in template, an inline plan, or a saved planId
Ingest a call with its recordingUrl, startedAt, interfaceType, callDirection, and transcript for analysis
Score selected calls or chats by creating a metric collection job with callIds or chatIds and metrics
Define custom metric definitions with thresholds and variants, and apply them through metric policies
GET STARTED
Model test callers with personas that set language, accent, gender, speech pace, and background noise
Author customer flows with a happy path and edge cases, and mock tool calls with tool fixtures
Subscribe a webhook to Roark events and open issues with call or chat evidence attached
Patterns agents use Roark Analytics API for, with concrete tasks.
★ AI coding agent that tests a voice agent before release
A coding agent editing a voice agent's prompt can ask Roark to run a test before the change ships. Through Jentic the agent searches for 'run a simulation against my voice agent', loads the Roark simulation-run operation with its input schema, and starts a run from a template or a saved plan with the bearer token added at call time. It then reads the plan job status and the resulting metrics to decide whether the prompt change is ready.
POST /v1/simulation/run with an existing planId, then poll GET /v1/simulation/plan/job/{jobId} until the job finishes and report the outcome
Post-call analytics for production calls
Teams running voice agents in production send each finished call to Roark with its recording URL, start time, interface type, direction, and transcript. A metric collection job then scores a batch of calls against the metrics the team cares about, and per-call metrics and sentiment runs can be read back by call id. This turns raw call logs into measurable quality signals.
POST /v1/call with recordingUrl, startedAt, interfaceType, and callDirection, then POST /v1/metric/collection-jobs with the new call id in callIds and the chosen metrics
Realistic test callers and flows
A simulation is only as good as its callers. Roark personas describe a caller's language, accent, gender, speech pace, speech clarity, background noise, and interruption behaviour, while customer flows define the happy path and edge cases a conversation should cover. Tool fixtures and tool mocks let the test agent's tool calls return controlled responses.
POST /v1/persona with name, language, accent, and gender for a fast-talking caller, then POST /v1/customer-flow/{flowId}/edge-case to add an interruption scenario to the refund flow
Quality issue tracking
When a metric drops or a reviewer spots a bad conversation, an issue can be opened through the API with a title, summary, severity, and the calls or chats as evidence in one transaction. Listing issues by status, source, or severity gives a running view of open quality problems across the project.
POST /v1/issue with the title 'Agent skips identity check', severity, and the two failing call ids as evidence
146 endpoints — the roark analytics api tests and monitors voice and chat ai agents: it runs simulated conversations against an agent and scores real calls and chats with metrics.
METHOD
PATH
DESCRIPTION
/v1/simulation/run
Run a simulation
/v1/simulation/plan/job/{jobId}
Get a simulation plan job
/v1/call
Create a call for analysis
/v1/call/{callId}/transcript
Get call transcript
/v1/call/{callId}/metrics
List call metrics
/v1/metric/collection-jobs
Create a metric collection job
/v1/persona
Create a persona
/v1/webhook
Create a webhook
/v1/simulation/run
Run a simulation
/v1/simulation/plan/job/{jobId}
Get a simulation plan job
/v1/call
Create a call for analysis
/v1/call/{callId}/transcript
Get call transcript
/v1/call/{callId}/metrics
List call metrics
/v1/metric/collection-jobs
Create a metric collection job
/v1/persona
Create a persona
/v1/webhook
Create a webhook
What agents get from Jentic-routed access to this vendor.
Setup
Wiring Roark by hand means handling bearer tokens that differ between personal credentials and project API keys, and learning how templates, run plans, plan jobs, and metric collection jobs relate. Through Jentic you install once, import Roark from the API Directory, store the token once, and your agent calls it.
Permission scoping
Roark puts the agent id in the URL path for agent and prompt calls (/v1/agent/{agentId}/prompts), so a rule can pin your agent to one Roark agent's prompts. Simulation runs carry their plan or template in the request body, so for those, rules bound which operations are allowed. You choose the operations it may call, so destructive ones like deleting an agent or revoking a project API key are not included unless you add them.
Credential isolation
Your Roark 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 'run a simulation against my voice agent' or 'get a call transcript', and Jentic returns the matching Roark operation with its input schema so the agent calls the right endpoint without browsing the reference docs.
Alternatives and complements available in the Jentic catalogue.
Specific to using Roark Analytics API through Jentic.
What authentication does the Roark Analytics API use?
Per its OpenAPI spec, the Roark Analytics API uses HTTP bearer authentication with a JWT-format token in the `Authorization` header. The spec also distinguishes personal credentials from project API keys, and some credential endpoints refuse a project API key. Through Jentic the token is held by your own instance and injected at call time, so the agent never sees it.
Can I run a test simulation against my agent with the Roark Analytics API?
Yes. POST /v1/simulation/run starts a simulation from a built-in template, an inline plan, or a saved planId, and returns the run. Plan jobs can be listed, read, and cancelled under /v1/simulation/plan/job/{jobId}. The older POST /v1/simulation/plan/{planId}/job call is deprecated in favour of the run endpoint.
What are the rate limits for the Roark Analytics API?
The OpenAPI spec does not specify rate limits. Check the Roark website at https://roark.ai or your Roark dashboard for current limits before scheduling large metric collection jobs.
Is there a Roark MCP server?
You do not need an MCP server to give your agent Roark. Jentic connects it directly from the API Directory: import it, store your token once, and your agent calls the simulation, call, and metric operations it needs on demand without loading another server's tool definitions into its context.
How do I score calls with my own metrics through Jentic?
Search Jentic for 'score calls with a metric', load the POST /v1/metric/collection-jobs operation, and execute it with callIds and the metrics to compute. Then read GET /v1/metric/collection-jobs/{jobId}/metric-values for the results. 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 Roark Analytics API?
Yes. For a release-check agent, write a rule that allows only POST /v1/simulation/run and GET /v1/simulation/plan/job/{jobId}, so it can start tests and read their results but cannot delete agents, revoke API keys, or remove project members. Every call it makes is logged.
For Agents
Run simulated test conversations against voice and chat AI agents, ingest real calls and transcripts, and score them with custom metrics, thresholds, and policies.
Use for: Run a simulation against my voice agent before I deploy the new prompt, Get the transcript of a call by its id, I want to score last week's calls with my resolution metric, Create a persona for an impatient caller with background noise
Not supported: Does not place production phone calls, host telephony numbers, or generate speech for your live agent. Use for testing, simulating, and scoring voice and chat agent conversations only.
The Roark Analytics API tests and monitors voice and chat AI agents: it runs simulated conversations against an agent and scores real calls and chats with metrics. Simulations can start from a built-in template, an inline plan, or a saved run plan, and use personas, environments, customer flows with edge cases, and tool fixtures that mock the agent's tool calls. Recorded calls and chats are ingested with their transcripts, then scored by metric definitions, thresholds, and policies through metric collection jobs. The same API manages agents and their prompts, webhooks, issues, managed agent configs with staging and production revisions, projects and members, and the benchmark leaderboard.
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.
Base layer of spec validity and structural soundness.
Aggregated quality score from linter diagnostics, weighted by severity.
Percentage of `$ref` references that resolve successfully.
Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).
Structural correctness score based on schema issues using logarithmic dampening.
Clarity, completeness, and ingestion readiness for developers and tooling.
How richly the API is illustrated with examples.
Percentage of examples that conform to their schemas.
Percentage of operations with complete response definitions (success, client error, server error).
Health of API ingestion, bundling, and resolution within Jentic pipelines.
Semantic breadth, depth, and agent comprehension for AI systems.
Coverage of descriptions across API elements.
Coverage of RFC 9457 Problem Details for error responses.
Coverage, uniqueness, and casing consistency of operationIds for AI inference.
Coverage of summaries across operations/tags/info.
Functional utility, complexity comfort, and AI orchestration readiness.
Agent comfort level based on API operational and structural complexity.
Trust, risk posture, and security compliance.
Average quality of security schemes based on authentication method strength (weakest link for OAuth2).
Findability, semantic richness, and reasoning readiness.
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>