Install Jentic One Beta
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Sentiyen 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%2Fsentiyen.com%2Fsentiyen" | 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%2Fsentiyen.com%2Fsentiyen" | 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 Sentiyen API.
Send a chat message (non-streaming)
Generate followup question suggestions
Record user feedback for a message
Query and filter Sentiyen API records by parameters
Monitor Sentiyen API operational status and events
GET STARTED
Patterns agents use Sentiyen API for, with concrete tasks.
★ Communications Operations
Use the Sentiyen API to perform communications operations programmatically. The API provides 3 endpoints covering core functionality including send a chat message (non-streaming), generate followup question suggestions, record user feedback for a message.
Call POST /chat/message to send a chat message (non-streaming)
Automated Messaging Management
Automate messaging operations by combining multiple Sentiyen API endpoints. Agents can generate followup question suggestions and then record user feedback for a message in a single workflow.
Call POST /chat/message/followup-suggestions to generate followup question suggestions, then verify the result
AI Agent Integration via Jentic
AI agents discover and call Sentiyen 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 apiKey tokens manually.
Search Jentic for 'send a chat message (non-streaming)', load the operation schema, and execute with Jentic-managed credentials
3 endpoints — sentiyen ai-powered q&a api for building conversational interfaces.
METHOD
PATH
DESCRIPTION
/chat/message
Send a chat message (non-streaming)
/chat/message/followup-suggestions
Generate followup question suggestions
/chat/message/feedback
Record user feedback for a message
/chat/message
Send a chat message (non-streaming)
/chat/message/followup-suggestions
Generate followup question suggestions
/chat/message/feedback
Record user feedback for a message
What agents get from Jentic-routed access to this vendor.
Setup
Wiring Sentiyen by hand means setting the X-API-Key header on every chat request and handling its message and feedback calls yourself. Through Jentic you install once, import Sentiyen from the API Directory, store the key once, and your agent calls it.
Permission scoping
Sentiyen carries the chat target in the request body, not the URL path, so limit the agent to the operations it needs, such as sending a chat message or requesting follow-up suggestions. You choose the operations it may call, so feedback submission is not included unless you add it.
Credential isolation
Your Sentiyen API 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 'send a chat message' or 'get follow-up suggestions', and Jentic returns the matching Sentiyen 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 Sentiyen API through Jentic.
What authentication does the Sentiyen API use?
The Sentiyen API uses an API key passed in the `X-API-Key` header. 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 send a chat message (non-streaming) with the Sentiyen API?
Yes. Use the POST /chat/message endpoint. The API returns structured JSON responses that agents can parse and act on directly.
What are the rate limits for the Sentiyen 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 send a chat message (non-streaming) through Jentic?
Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'send a chat message (non-streaming)'. Jentic returns the matching Sentiyen API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.
How many endpoints does the Sentiyen API have?
The Sentiyen API exposes 3 endpoints covering messaging operations.
Can I limit what my agent is allowed to do with the Sentiyen API?
Yes. Because you run Jentic One yourself, your own rules decide which Sentiyen operations and credentials the agent may use. Since Sentiyen carries the chat target in the request body rather than the URL path, you scope access at the operation level, allowing only what the agent needs such as sending a chat message or requesting follow-up suggestions. You choose the operations it may call, so feedback submission stays out of reach unless you explicitly add it.
For Agents
Programmatically send a chat message (non-streaming), generate followup question suggestions. Covers 3 operations with apiKey authentication.
Use for: I need to send a chat message (non-streaming), I want to generate followup question suggestions, Search for record user feedback for a message, List all records from Sentiyen API
Not supported: Does not handle payments, crm, or developer tools - use for communications only.
Sentiyen AI-powered Q&A API for building conversational interfaces. Supports streaming and non-streaming message generation with references and followup questions. The API exposes 3 endpoints secured with apiKey authentication.
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>