Install Jentic One Beta

Connect the Provet Cloud REST API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Provet Cloud REST 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%2Fprovetcloud.com%2Fprovetcloud" | 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%2Fprovetcloud.com%2Fprovetcloud" | 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 Provet Cloud REST API.

List clients

Get a client

Create a patient

Use Cases

Patterns agents use Provet Cloud REST API for, with concrete tasks.

★ Healthcare Operations

Use the Provet Cloud REST API to perform healthcare operations programmatically. The API provides 30 endpoints covering core functionality including list clients, get a client, create a patient.

Call GET /client/ to list clients

GET STARTED

Start building with Provet Cloud REST API

Explore with Jentic One

View OpenAPI Document

Automated Appointment Management

Automate appointment operations by combining multiple Provet Cloud REST API endpoints. Agents can get a client and then create a patient in a single workflow.

Call GET /client/{clientId}/ to get a client, then verify the result

AI Agent Integration via Jentic

AI agents discover and call Provet Cloud REST 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 bearer, oauth2 tokens manually.

Search Jentic for 'list clients', load the operation schema, and execute with Jentic-managed credentials

Key Endpoints

30 endpoints — provet cloud's rest api offers most of the key provet data to be read or manipulated by other systems.

METHOD

PATH

DESCRIPTION

GET

/client/

List clients

GET

/client/{clientId}/

Get a client

POST

/patient/

Create a patient

GET

/patient/

List patients

GET

/patient/{patientId}/

Get a patient

GET

/consultation/

List consultations

GET

/consultation/{consultationId}/

Get a consultation

POST

/appointment/

Create an appointment

GET

/client/

List clients

GET

/client/{clientId}/

Get a client

POST

/patient/

Create a patient

GET

/patient/

List patients

GET

/patient/{patientId}/

Get a patient

GET

/consultation/

List consultations

GET

/consultation/{consultationId}/

Get a consultation

POST

/appointment/

Create an appointment

Why Jentic?

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

Setup

Wiring the Provet Cloud REST API by hand means running its OAuth2 flow, keeping tokens fresh, and pinning requests to your own provetId host. Through Jentic you install once, import Provet Cloud from the API Directory, store the credential once, and your agent calls it.

Permission scoping

Provet Cloud puts the resource id in the URL path (/patient/{patientId}/, /client/{clientId}/, /consultation/{consultationId}/), so a rule can pin your agent to reading a specific patient or client. You choose the operations it may call, so writes like creating a patient or appointment are not included unless you add them.

Credential isolation

Your Provet Cloud REST API credential 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 'list clients' or 'read a patient record', and Jentic returns the matching Provet Cloud operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

FAQs

Specific to using Provet Cloud REST API through Jentic.

What authentication does the Provet Cloud REST API use?

The Provet Cloud REST API uses bearer, oauth2 authentication. 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 list clients with the Provet Cloud REST API?

Yes. Use the GET /client/ endpoint. The API returns structured JSON responses that agents can parse and act on directly.

What are the rate limits for the Provet Cloud REST 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 list clients through Jentic?

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

How many endpoints does the Provet Cloud REST API have?

The Provet Cloud REST API exposes 30 endpoints covering appointment, appointment_reminder, client operations.

Can I limit what my agent is allowed to do with the Provet Cloud REST API?

Yes. Jentic One runs self-hosted, so your own rules decide which Provet Cloud operations and credentials your agent may use. Because Provet Cloud puts the resource id in the URL path, such as /patient/{patientId}/, /client/{clientId}/, and /consultation/{consultationId}/, you can pin the agent to reading a specific patient, client, or consultation. You also choose the operations it may call, so writes like creating a patient or an appointment are excluded unless you add them.

Provet Cloud REST API

Name: Provet Cloud REST API
Brand: Provet Cloud REST API
Availability: InStock

AI ReadinessAI-Aware (B)66/100

See full scorecard

Official vendor OpenAPI document · agent-readyHealthcareAppointment Schedulingbearer, oauth230 EndpointsREST

For Agents

Programmatically list clients, get a client. Covers 30 operations with bearer, oauth2 authentication.

Use for: I need to clients, I want to a client, Search for a patient, Find all patients

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

Provet Cloud's REST API offers most of the key Provet data to be read or manipulated by other systems. It provides access to veterinary practice management data including patients, clients, consultations, appointments, invoices, prescriptions, and online booking. The API exposes 30 endpoints secured with bearer, oauth2 authentication.

Jentic One on Github View OpenAPI Document

Show dimension breakdown

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: BSignals: 4

83%

Lint Results

Aggregated quality score from linter diagnostics, weighted by severity.

100%

Resolution Completeness

Percentage of `$ref` references that resolve successfully.

Specification Validity

Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).

75%

Structural Integrity

Structural correctness score based on schema issues using logarithmic dampening.

Developer Experience & Jentic Compatibility

Clarity, completeness, and ingestion readiness for developers and tooling.

Grade: B-Signals: 4

Example Density

How richly the API is illustrated with examples.

100%

Example Validity

Percentage of examples that conform to their schemas.

50%

Response Coverage

Percentage of operations with complete response definitions (success, client error, server error).

93%

Tooling Readiness

Health of API ingestion, bundling, and resolution within Jentic pipelines.

AI-Readiness & Agent Experience

Semantic breadth, depth, and agent comprehension for AI systems.

Grade: D+Signals: 4

47%

Description Coverage

Coverage of descriptions across API elements.

Error Standardization

Coverage of RFC 9457 Problem Details for error responses.

100%

OperationId Quality

Coverage, uniqueness, and casing consistency of operationIds for AI inference.

53%

Summary Coverage

Coverage of summaries across operations/tags/info.

Agent Usability

Functional utility, complexity comfort, and AI orchestration readiness.

Grade: A+Signals: 1

94%

Complexity Comfort

Agent comfort level based on API operational and structural complexity.

Security

Trust, risk posture, and security compliance.

Grade: A-Signals: 1

72%

Authentication Strength

Average quality of security schemes based on authentication method strength (weakest link for OAuth2).

AI Discoverability

Findability, semantic richness, and reasoning readiness.

Grade: ASignals: 1

82%

Descriptive Richness

Clarity and depth of descriptions across API elements.

Connect the Provet Cloud REST API to your agent

Capabilities

Use Cases

Start building with Provet Cloud REST API

Key Endpoints

Why Jentic?

Related APIs

FAQs

Provet Cloud REST API

Jentic AI Readiness Score

Provet Cloud REST API

Foundational Compliance

Lint Results

Resolution Completeness

Specification Validity

Structural Integrity

Developer Experience & Jentic Compatibility

Example Density

Example Validity

Response Coverage

Tooling Readiness

AI-Readiness & Agent Experience

Description Coverage

Error Standardization

OperationId Quality

Summary Coverage

Agent Usability

Complexity Comfort

Security

Authentication Strength

AI Discoverability

Descriptive Richness