Install Jentic One Beta

Connect the Savio API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Savio 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%2Fsavio.io%2Fsavio" | sh

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%2Fsavio.io%2Fsavio" | sh
jentic register       # connects your agent to your Jentic One instance

Jentic 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 Savio API.

Create feedback

List feedback

Get feedback by ID

Query and filter Savio API records by parameters

Monitor Savio API operational status and events

Use Cases

GET STARTED

Start building with Savio API

Explore with Jentic One

View OpenAPI Document

Automated Feedback Management

Automate feedback operations by combining multiple Savio API endpoints. Agents can list feedback and then get feedback by id in a single workflow.

Call GET /feedback/ to list feedback, then verify the result

AI Agent Integration via Jentic

AI agents discover and call Savio 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 'create feedback', load the operation schema, and execute with Jentic-managed credentials

Key Endpoints

9 endpoints — savio tracks feature requests from survey and nps tools, help desks, crms, or from any customer-facing tool where you receive them.

METHOD

PATH

DESCRIPTION

POST

/create-feedback/

Create feedback

GET

/feedback/

List feedback

GET

/feedback/{id}/

Get feedback by ID

GET

/feature-requests/

List feature requests

GET

/feature-requests/{id}/

Get feature request by ID

POST

/users/

Create or update a contact

GET

/users/

List contacts

POST

/companies/

Create or update a company

POST

/create-feedback/

Create feedback

GET

/feedback/

List feedback

GET

/feedback/{id}/

Get feedback by ID

GET

/feature-requests/

List feature requests

GET

/feature-requests/{id}/

Get feature request by ID

POST

/users/

Create or update a contact

GET

/users/

List contacts

POST

/companies/

Create or update a company

Why Jentic?

What agents get from Jentic-routed access to this vendor.

Setup

Wiring the Savio API by hand means formatting its token as a Token-prefixed Authorization header and coordinating feedback, feature request, user, and company calls yourself. Through Jentic you install once, import the Savio API from the API Directory, store the token once, and your agent calls it.

Permission scoping

Savio puts the feedback and feature-request id in the URL path (/feedback/{id}/ and /feature-requests/{id}/), so a rule can pin your agent to one feedback item. You choose the operations it may call, so a write like creating feedback or a user is not included unless you add it alongside the reads.

Credential isolation

Your Savio API 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 'create feedback' or 'list feature requests', and Jentic returns the matching Savio API operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

FAQs

Specific to using Savio API through Jentic.

What authentication does the Savio API use?

The Savio API uses an API key passed in the `Authorization` 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 create feedback with the Savio API?

Yes. Use the POST /create-feedback/ endpoint. The API returns structured JSON responses that agents can parse and act on directly.

What are the rate limits for the Savio 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 feedback through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'create feedback'. Jentic returns the matching Savio API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

How many endpoints does the Savio API have?

The Savio API exposes 9 endpoints covering feedback, feature requests, contacts operations.

Can I limit what my agent is allowed to do with the Savio API?

Yes. Jentic One is self-hosted by you, so your own rules decide which Savio API operations and credentials your agent may use. Because Savio puts the feedback and feature-request id in the URL path (/feedback/{id}/ and /feature-requests/{id}/), a rule can pin the agent to a single feedback item or feature request. You choose the operations it may call, so a write such as POST /create-feedback/ or POST /users/ is not included unless you add it alongside the read endpoints.

Savio API

Name: Savio API
Brand: Savio API
Availability: InStock

Official vendor OpenAPI document · agent-readyCRMContact ManagementapiKey9 EndpointsREST

For Agents

Programmatically create feedback, list feedback. Covers 9 operations with apiKey authentication.

Use for: I need to feedback, I want to feedback, Search for feedback by id, Find all feature requests

Not supported: Does not handle payments, communications, or developer tools - use for crm only.

Savio tracks feature requests from survey and NPS tools, help desks, CRMs, or from any customer-facing tool where you receive them. This API allows managing feedback, feature requests, contacts, and companies. The API exposes 9 endpoints secured with apiKey authentication.

Jentic One on Github View OpenAPI Document

Connect the Savio API to your agent

Capabilities

Use Cases

Start building with Savio API

Key Endpoints

Why Jentic?

Related APIs

FAQs

Savio API