Install Jentic One Beta
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the ClosedLoop AI 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%2Fclosedloop.sh%2Fclosedloop" | 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%2Fclosedloop.sh%2Fclosedloop" | 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 ClosedLoop AI API.
List and create customer feedback records
Read the detail of a specific feedback item, including newly captured ones
List the raw customer inputs behind the feedback
Start AI chat conversations and process messages to analyze feedback
Generate a title for a feedback conversation automatically
GET STARTED
Track account usage records
Patterns agents use ClosedLoop AI API for, with concrete tasks.
★ Agent-driven feedback triage
An AI agent processing an inbox of customer messages can create feedback records in ClosedLoop and pull the newly captured items for review. Because the API separates raw inputs from structured feedback, the agent can trace any feedback item back to the customer input that produced it before deciding what to escalate.
Create a feedback record from a customer message, then list the new feedback and read the raw input behind one item
Feedback analysis conversations
Understanding a batch of feedback often takes back-and-forth questioning. ClosedLoop supports AI chat conversations where messages are processed against the feedback data, so a user or agent can ask what themes are emerging and get an answer grounded in the stored feedback. Conversation titles are generated automatically for later reference.
Create a conversation, send a message asking which themes dominate recent feedback, and process it to get an answer
Input-to-insight pipeline
Teams that collect feedback from several sources need it in one analyzable place. The API ingests customer inputs, lists integrations that feed them, and exposes the feedback derived from them, so a pipeline can move source inputs through to structured, reviewable feedback and track usage along the way.
List the configured integrations and the customer inputs, then read the feedback derived from them
20 endpoints — the closedloop ai api powers a customer-feedback analysis platform, turning raw customer inputs into structured feedback that teams can review and act on.
METHOD
PATH
DESCRIPTION
/feedbacks
List feedback records
/feedbacks
Create a feedback record
/feedbacks/{id}
Get feedback detail
/inputs
List customer inputs
/chat/conversations
Create a conversation
/chat/conversations/{id}/process
Process a message with AI over the feedback
/usage
List usage records
/feedbacks
List feedback records
/feedbacks
Create a feedback record
/feedbacks/{id}
Get feedback detail
/inputs
List customer inputs
/chat/conversations
Create a conversation
/chat/conversations/{id}/process
Process a message with AI over the feedback
/usage
List usage records
What agents get from Jentic-routed access to this vendor.
Setup
Wiring the ClosedLoop AI API by hand means handling its API key in the Authorization header, its separate inputs-versus-feedback model, and its chat-processing flow yourself. Through Jentic you install once, import ClosedLoop from the API Directory, store the key once, and your agent calls it.
Permission scoping
Records are addressed by an id in the URL path, but a rule bounds which operations your agent may call rather than which record it touches. You choose the operations it may call, such as reading feedback and conversations, so creating records or changing team settings is not included unless you add it.
Credential isolation
Your ClosedLoop key 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 'analyze customer feedback' or 'list new feedback', and Jentic returns the matching ClosedLoop operation with its input schema so the agent calls the right endpoint without reading the reference docs.
Alternatives and complements available in the Jentic catalogue.
Specific to using ClosedLoop AI API through Jentic.
What authentication does the ClosedLoop AI API use?
The ClosedLoop AI API authenticates with an API key sent in the Authorization header, as declared in its OpenAPI spec. The health check needs no key. Through Jentic the key is stored once and injected at call time, so it never appears in your agent's prompt or logs.
Can I trace a feedback item back to its source with the ClosedLoop AI API?
Yes. The API keeps raw customer inputs separate from structured feedback and lets you list and read both, so an agent can follow a feedback item back to the customer input that produced it.
What are the rate limits for the ClosedLoop AI API?
The OpenAPI spec does not state numeric rate limits for the ClosedLoop AI API. Check the vendor documentation at https://closedloop.sh for current limits before processing feedback in bulk.
How do I analyze feedback through Jentic with the ClosedLoop AI API?
Search Jentic for 'analyze customer feedback', which returns the POST /chat/conversations/{id}/process operation with its input schema, then create a conversation and process a message. 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 ClosedLoop AI API?
Yes. Write a rule that allows only the feedback and conversation read operations, so the agent can review feedback and read analysis but cannot create records or change team settings, and every call it makes is logged. You decide which operations are in the rule, so nothing beyond reads runs unless you add it.
For Agents
Analyze customer feedback: list and create feedback records, read the raw inputs behind them, and run AI chat conversations that process feedback into insights.
Use for: List the latest customer feedback, Create a feedback record from a support message, Start a conversation to analyze a piece of feedback, Process a message through the feedback analysis model
Not supported: Does not handle support ticketing, live chat, or CRM records. Use for customer feedback analysis only.
The ClosedLoop AI API powers a customer-feedback analysis platform, turning raw customer inputs into structured feedback that teams can review and act on. It lists and creates feedback records, surfaces newly captured feedback, and exposes the raw inputs behind each item. AI chat conversations let a user or agent process feedback into insights, with conversation titles generated automatically.
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>