Install Jentic One Beta
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Review Harvest 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%2Freviewharvest.com%2Freviewharvest" | 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%2Freviewharvest.com%2Freviewharvest" | 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 Review Harvest API.
Create a new integration
Delete an integration
Validate API connection
Add a contact
Monitor Review Harvest API operational status and events
GET STARTED
Patterns agents use Review Harvest API for, with concrete tasks.
★ CRM Operations
Use the Review Harvest API to perform crm operations programmatically. The API provides 4 endpoints covering core functionality including create a new integration, delete an integration, validate API connection.
Call POST /create to create a new integration
Automated Authentication Management
Automate authentication operations by combining multiple Review Harvest API endpoints. Agents can delete an integration and then validate API connection in a single workflow.
Call GET /delete/{id} to delete an integration, then verify the result
AI Agent Integration via Jentic
AI agents discover and call Review Harvest 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 a new integration', load the operation schema, and execute with Jentic-managed credentials
4 endpoints — review harvest is a review management platform.
METHOD
PATH
DESCRIPTION
/create
Create a new integration
/delete/{id}
Delete an integration
/connection
Validate API connection
/add
Add a contact
/create
Create a new integration
/delete/{id}
Delete an integration
/connection
Validate API connection
/add
Add a contact
What agents get from Jentic-routed access to this vendor.
Setup
Wiring the Review Harvest API by hand means appending its api_key query parameter to every request, pointing calls at the integration host on integrations.reviewharvest.com, and handling retries yourself. Through Jentic you install once, import the Review Harvest API from the API Directory, store the API key once, and your agent calls it.
Permission scoping
Review Harvest's integration targets travel in the request body and query rather than as a resource you can pin, so limit the agent to the operations it needs, such as creating a connection or adding an integration. You choose that set, so operations like deleting an integration are not included unless you add them.
Credential isolation
Your Review Harvest 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 'create a new integration' or 'test a connection', and Jentic returns the matching Review Harvest 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.
Specific to using Review Harvest API through Jentic.
What authentication does the Review Harvest API use?
The Review Harvest API uses an API key passed in the `api_key` query. 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 a new integration with the Review Harvest API?
Yes. Use the POST /create endpoint. The API returns structured JSON responses that agents can parse and act on directly.
What are the rate limits for the Review Harvest 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 a new integration through Jentic?
Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'create a new integration'. Jentic returns the matching Review Harvest API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.
How many endpoints does the Review Harvest API have?
The Review Harvest API exposes 4 endpoints covering authentication, contacts, integrations operations.
Can I limit what my agent is allowed to do with the Review Harvest API?
Yes. Because Review Harvest's integration targets travel in the request body and query rather than as a resource you can pin, you scope the agent by choosing exactly which operations it may call in your self-hosted Jentic One instance, where your own rules decide the permitted operations and credentials. You might allow it to validate a connection with POST /connection, create an integration with POST /create, and add a contact with POST /add, while withholding the destructive GET /delete/{id} that removes an integration. Only the operations you grant are available to the agent, and the API key stays encrypted and injected at execution time so it never enters the agent's context.
For Agents
Programmatically create a new integration, delete an integration. Covers 4 operations with apiKey authentication.
Use for: I need to a new integration, I want to an integration, Search for validate API connection, Find all add a contact
Not supported: Does not handle payments, communications, or developer tools - use for crm only.
Review Harvest is a review management platform. The API supports creating integrations, managing contacts, and validating connections. The API exposes 4 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>