Install Jentic One Beta

Connect the Propetware API to your agent

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

Create a customer with firstName, lastName, and email, and add pets with a name and species such as dog or cat

Record and update notes on a customer, a pet, or an order

Create, update, and delete pet vaccination records and define vaccination types

List bookings filtered by date, status, pet, customer, kennel, or order

List orders by start and end date, status, customer, or pet

GET STARTED

Start building with Propetware API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use Propetware API for, with concrete tasks.

★ Agent-Run Front Desk Lookups

An AI agent connected through Jentic answers front desk questions for a boarding kennel: it searches customers by email or name with the q parameter, lists the customer's pets, checks vaccination records before a stay, and adds a note to the order when the owner calls with instructions. Staff get answers in chat without switching screens.

Search customers in account 101 by email jane@example.com, list her pets, list each pet's vaccinations, and create an order note on order 5521 saying pickup is after 6pm

Daily Arrivals and Departures Report

Each morning a script lists bookings for the day with the booking date filter, groups them by kennel, and flags pets whose vaccination records need review. The kennel and order filters on the bookings list let the report drill into one run or one stay.

List bookings for account 101 on 2026-11-13, group them by kennelId, and report which pets have vaccinations to review

New Customer Intake

When a new owner fills in a web form, the intake flow creates the customer with firstName, lastName, and email, adds each pet with a name and species, and records vaccination details. Optional flags such as sendWelcomeEmail control whether Propetware emails the new customer.

Create customer Sam Lee with email sam@example.com in account 101, then create a pet named Biscuit with species dog for that customer

Event-Driven Sync

A business keeps its marketing list or accounting tool in step with Propetware by subscribing a webhook to events such as customer.created, order.created, booking.checkedIn, and booking.checkedOut. A test operation fires a webhook.test event, and the deliveries list shows what was sent.

Create a webhook to https://example.com/hooks with events booking.checkedIn and booking.checkedOut, then send a test event and read its deliveries

Key Endpoints

110 endpoints — the propetware api reads and updates the customer and pet records behind a pet care business running on propetware, such as a boarding kennel, daycare, or grooming shop.

METHOD

PATH

DESCRIPTION

GET

/accounts/{accountId}/customers

List or search customers

POST

/accounts/{accountId}/customers

Create a customer

POST

/accounts/{accountId}/customers/{customerId}/pets

Create a pet

GET

/accounts/{accountId}/bookings

List bookings

GET

/accounts/{accountId}/orders

List orders

GET

/accounts/{accountId}/pets/{petId}/vaccinations

List pet vaccinations

POST

/accounts/{accountId}/orders/{orderId}/notes

Create an order note

POST

/webhooks

Create a webhook

GET

/accounts/{accountId}/customers

List or search customers

POST

/accounts/{accountId}/customers

Create a customer

POST

/accounts/{accountId}/customers/{customerId}/pets

Create a pet

GET

/accounts/{accountId}/bookings

List bookings

GET

/accounts/{accountId}/orders

List orders

GET

/accounts/{accountId}/pets/{petId}/vaccinations

List pet vaccinations

POST

/accounts/{accountId}/orders/{orderId}/notes

Create an order note

POST

/webhooks

Create a webhook

Why Jentic?

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

Setup

Wiring Propetware by hand means sending the `X-API-Key` header, threading the accountId through nearly every path, and backing off on 429s using `X-RateLimit-Remaining` and Retry-After. Through Jentic you install once, import Propetware from the API Directory, store the key once, and your agent calls it.

Permission scoping

Propetware puts the account id in the URL path (/accounts/{accountId}/...), and customer, pet, and order ids follow it, so a rule can pin your agent to one account, or one customer, and the operations you pick. You choose the operations it may call, so destructive ones like deleting notes, vaccination records, or webhooks are not included unless you add them.

Credential isolation

Your Propetware 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 'list pet bookings for a date' or 'check a pet's vaccinations', and Jentic returns the matching Propetware operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

FAQs

Specific to using Propetware API through Jentic.

What authentication does the Propetware API use?

Per its OpenAPI spec, the account, customer, pet, booking, product, and webhook operations authenticate with an API key in the `X-API-Key` header (scheme ApiKeyAuth). The spec also declares an alternate form, the key sent as `Authorization: ApiKey <key>` (scheme ApiKeyAuthAlt), and a JWT bearer token (scheme BearerAuth) that the auth refresh, logout, and me operations use after a customer logs in with email and password. Through Jentic the key is stored encrypted by your own Jentic One instance and injected at call time.

What are the rate limits for the Propetware API?

The Propetware OpenAPI spec states a deployed default of 600 requests per minute per API client, in a sixty-second window that opens on the first counted request. It tells clients to read the real ceiling from `X-RateLimit-Limit` and the remaining budget from `X-RateLimit-Remaining`, and to honor Retry-After on a 429, which is never processed and so is always safe to retry.

Can I check a pet's vaccinations with the Propetware API?

Yes. You can list a pet's vaccination records, create a new record, update or delete one, and list the vaccination types the account defines. Preventive records and pet documents have their own list operations, and documents can be downloaded.

Is there a Propetware MCP server?

You don't need an MCP server to give your agent Propetware. Jentic connects it directly from the API Directory: import it, store your credential once, and your agent calls it, finding operations on demand instead of loading every tool definition into its context.

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

Yes. For example, write a rule that allows only the customer list, pet list, vaccination list, and order note create operations under /accounts/101, so the agent can look up owners and pets for that one business and leave order notes, while note deletion, custom field changes, and webhook management stay out of reach. Every call it makes is logged.

How do I list a day's bookings with the Propetware API through Jentic?

Import the Propetware API from the Jentic API Directory, store your API key once, and have your agent search Jentic for 'list pet bookings for a date'. Jentic returns the list bookings operation with its input schema, including the accountId path parameter and filters for date, status, pet, customer, and kennel. To run it on your own infrastructure, install Jentic One from its GitHub repo.

Which webhook events does Propetware send?

The webhook create operation takes a url and a list of events, including customer.created, pet.updated, order.created, order.changeRequested, order.cancelled, booking.checkedIn, booking.checkedOut, note.created, and vaccination.updated, among others. A test operation sends a webhook.test event, and a deliveries operation lists what was sent to each webhook.

Propetware API

AI ReadinessAI-Aware (B-)61/100

See full scorecard

Official vendor OpenAPI document · agent-readyCRMContact ManagementapiKey, bearer110 EndpointsREST

For Agents

Look up and update pet care customers, pets, notes, and vaccination records, list orders and bookings, read the service menu, and subscribe to booking and order webhooks in Propetware.

Use for: Find the customer with this email address, Add a new dog named Biscuit to the Murphy household, List all bookings checking in tomorrow, Check whether this pet's rabies vaccination is on file

Not supported: Does not take payments, process invoices, or keep veterinary clinical records. Use for pet care customers, pets, bookings, notes, and vaccination records in Propetware only.

The Propetware API reads and updates the customer and pet records behind a pet care business running on Propetware, such as a boarding kennel, daycare, or grooming shop. It creates and updates customers and their pets, records notes against customers, pets, and orders, and manages vaccination records and vaccination types. It lists orders and bookings with date, status, pet, and kennel filters, exposes the service menu of rates, add-ons, classes, grooming, and training, and sends webhooks for events such as order.created and booking.checkedIn.

Jentic One on Github View OpenAPI Document

Show dimension breakdown

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: C-Signals: 4

91%

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).

21%

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.

92%

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).

100%

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: C-Signals: 4

48%

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.

59%

Summary Coverage

Coverage of summaries across operations/tags/info.

Agent Usability

Functional utility, complexity comfort, and AI orchestration readiness.

Grade: ASignals: 1

82%

Complexity Comfort

Agent comfort level based on API operational and structural complexity.

Security

Trust, risk posture, and security compliance.

Grade: C+Signals: 1

58%

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: A-Signals: 1

73%

Descriptive Richness

Clarity and depth of descriptions across API elements.

Connect the Propetware API to your agent

Capabilities

Start building with Propetware API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

Propetware API

Jentic AI Readiness Score

Propetware 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