Install Jentic One Beta
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Revi Reviews 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%2Frevi.io%2Frevi" | 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%2Frevi.io%2Frevi" | 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 Revi Reviews API.
Test connection
Create orders
Update status of orders
Link products to orders
Get product review info
GET STARTED
Patterns agents use Revi Reviews API for, with concrete tasks.
★ E-Commerce Operations
Use the Revi Reviews API to perform e commerce operations programmatically. The API provides 8 endpoints covering core functionality including test connection, create orders, update status of orders.
Call POST /hello_world to test connection
Automated Quickstart Management
Automate quickstart operations by combining multiple Revi Reviews API endpoints. Agents can create orders and then update status of orders in a single workflow.
Call POST /orders to create orders, then verify the result
AI Agent Integration via Jentic
AI agents discover and call Revi Reviews 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 'test connection', load the operation schema, and execute with Jentic-managed credentials
8 endpoints — rest api for interacting with the revi.
METHOD
PATH
DESCRIPTION
/hello_world
Test connection
/orders
Create orders
/orders_status
Update status of orders
/products
Create products
/orders_products
Link products to orders
/product_info
Get product review info
/reviews
Get reviews
/shop_info
Get shop rating info
/hello_world
Test connection
/orders
Create orders
/orders_status
Update status of orders
/products
Create products
/orders_products
Link products to orders
/product_info
Get product review info
/reviews
Get reviews
/shop_info
Get shop rating info
What agents get from Jentic-routed access to this vendor.
Setup
Wiring the Revi Reviews API by hand means handling its X-API-KEY header auth, passing that key on every call to api.revi.io, and managing retries yourself. Through Jentic you install once, import the Revi Reviews API from the API Directory, store the API key once, and your agent calls it.
Permission scoping
Revi's targets travel in the request body and query rather than as a resource id you can pin, so limit the agent to the operations it needs, such as reading product info or listing reviews. You choose that set, so write operations like posting orders or products are not included unless you add them.
Credential isolation
Your Revi 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 'read shop info' or 'list product reviews', and Jentic returns the matching Revi Reviews API 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.
Stripe
Alternative e commerce API
Choose Stripe when you need a different approach to e commerce operations
Specific to using Revi Reviews API through Jentic.
What authentication does the Revi Reviews API use?
The Revi Reviews 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 test connection with the Revi Reviews API?
Yes. Use the POST /hello_world endpoint. The API returns structured JSON responses that agents can parse and act on directly.
What are the rate limits for the Revi Reviews 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 test connection through Jentic?
Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'test connection'. Jentic returns the matching Revi Reviews API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.
How many endpoints does the Revi Reviews API have?
The Revi Reviews API exposes 8 endpoints covering quickstart, orders, products operations.
Can I limit what my agent is allowed to do with the Revi Reviews API?
Yes. Because you run Jentic One yourself, your own rules decide which Revi Reviews API operations and credentials the agent can use, and Revi's targets travel in the request body and query rather than as a resource id you can pin, so you scope access by operation. You can allow the agent only read calls such as GET /product_info, GET /reviews, and GET /shop_info, leaving write operations like POST /orders, POST /products, and POST /orders_status out unless you add them. The stored API key is injected at execution time for the operations you permit, so the agent cannot reach endpoints outside that set.
For Agents
Programmatically test connection, create orders. Covers 8 operations with apiKey authentication.
Use for: I need to test connection, I want to orders, Search for status of orders, Find all products
Not supported: Does not handle payments, communications, or crm - use for e-commerce only.
REST API for interacting with the Revi.io reviews platform. Manage orders, products, and reviews for your e-commerce shop. The API exposes 8 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>