Install Jentic One Beta

Connect the PropertyInspect API to your agent

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

Redirect user to request integration

Exchange authorization code or refresh token

Create a property

List properties

Get a property

GET STARTED

Start building with PropertyInspect API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use PropertyInspect API for, with concrete tasks.

★ CRM Operations

Use the PropertyInspect API to perform crm operations programmatically. The API provides 57 endpoints covering core functionality including redirect user to request integration, exchange authorization code or refresh token, create a property.

Call GET /oauth/authorize to redirect user to request integration

Automated Authentication Management

Automate authentication operations by combining multiple PropertyInspect API endpoints. Agents can exchange authorization code or refresh token and then create a property in a single workflow.

Call POST /oauth/token to exchange authorization code or refresh token, then verify the result

AI Agent Integration via Jentic

AI agents discover and call PropertyInspect 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 tokens manually.

Search Jentic for 'redirect user to request integration', load the operation schema, and execute with Jentic-managed credentials

Key Endpoints

57 endpoints — api for managing property inspections, properties, contacts, custom fields, actions, and attachments for property inspection workflows.

METHOD

PATH

DESCRIPTION

GET

/oauth/authorize

Redirect user to request integration

POST

/oauth/token

Exchange authorization code or refresh token

POST

/properties

Create a property

GET

/properties

List properties

GET

/properties/{propertyId}

Get a property

PUT

/properties/{propertyId}

Update a property

POST

/properties/{propertyId}/meters

Create a meter

GET

/properties/{propertyId}/meters

List property meters

GET

/oauth/authorize

Redirect user to request integration

POST

/oauth/token

Exchange authorization code or refresh token

POST

/properties

Create a property

GET

/properties

List properties

GET

/properties/{propertyId}

Get a property

PUT

/properties/{propertyId}

Update a property

POST

/properties/{propertyId}/meters

Create a meter

GET

/properties/{propertyId}/meters

List property meters

Why Jentic?

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

Setup

Wiring the PropertyInspect API by hand means running its OAuth authorize and token exchange, sending the bearer token on each call, and managing property records yourself. Through Jentic you install once, import PropertyInspect from the API Directory, store the credential once, and your agent calls it.

Permission scoping

PropertyInspect puts the property id in the URL path (/properties/{propertyId}), so a rule can pin your agent to one property: it can read that property and its meters and nothing else. You choose the operations it may call, so writes like updating a property are not included unless you add them.

Credential isolation

Your PropertyInspect 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 properties' or 'read a property's meters', and Jentic returns the matching PropertyInspect operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

FAQs

Specific to using PropertyInspect API through Jentic.

What authentication does the PropertyInspect API use?

The PropertyInspect API uses a Bearer token 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 redirect user to request integration with the PropertyInspect API?

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

What are the rate limits for the PropertyInspect 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 redirect user to request integration through Jentic?

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

How many endpoints does the PropertyInspect API have?

The PropertyInspect API exposes 57 endpoints covering authentication, properties, meters operations.

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

Yes. Because you run Jentic One yourself, your own rules decide which PropertyInspect operations and credentials the agent may use. Since PropertyInspect puts the property id in the URL path (/properties/{propertyId}), a rule can pin your agent to a single property so it reads only that property and its meters through GET /properties/{propertyId} and GET /properties/{propertyId}/meters. You pick the operations it may call, so writes such as POST /properties or PUT /properties/{propertyId} stay off unless you add them.

PropertyInspect API

Name: PropertyInspect API
Brand: PropertyInspect API
Availability: InStock

AI ReadinessAI-Aware (B)65/100

See full scorecard

Official vendor OpenAPI document · agent-readyCRMContact Managementbearer57 EndpointsREST

For Agents

Programmatically redirect user to request integration, exchange authorization code or refresh token. Covers 57 operations with bearer authentication.

Use for: I need to redirect user to request integration, I want to exchange authorization code or refresh token, Search for a property, Find all properties

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

API for managing property inspections, properties, contacts, custom fields, actions, and attachments for property inspection workflows. The API exposes 57 endpoints secured with bearer authentication.

Jentic One on Github View OpenAPI Document

Show dimension breakdown

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: ASignals: 4

98%

Lint Results

Aggregated quality score from linter diagnostics, weighted by severity.

100%

Resolution Completeness

Percentage of `$ref` references that resolve successfully.

100%

Specification Validity

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

42%

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

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: D+Signals: 4

39%

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.

58%

Summary Coverage

Coverage of summaries across operations/tags/info.

Agent Usability

Functional utility, complexity comfort, and AI orchestration readiness.

Grade: A+Signals: 1

93%

Complexity Comfort

Agent comfort level based on API operational and structural complexity.

Security

Trust, risk posture, and security compliance.

Grade: B-Signals: 1

60%

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: BSignals: 1

66%

Descriptive Richness

Clarity and depth of descriptions across API elements.

Connect the PropertyInspect API to your agent

Capabilities

Start building with PropertyInspect API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

PropertyInspect API

Jentic AI Readiness Score

PropertyInspect 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