Install Jentic One Beta

Connect the Quantiv API to your agent

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

Get Lead Property Details

Create EngagePro™ - Lead Widget

Access Quantiv API analytics resources via REST API

Use Cases

Patterns agents use Quantiv API for, with concrete tasks.

★ Analytics Operations

Use the Quantiv API to perform analytics operations programmatically. The API provides 14 endpoints covering core functionality including get lead property details, get lead property details, get buyer insights.

Call GET /api/v1/address-info to get lead property details

GET STARTED

Start building with Quantiv API

Explore with Jentic One

View OpenAPI Document

Automated Lead Append Level 1 Management

Automate lead append level 1 operations by combining multiple Quantiv API endpoints. Agents can get lead property details and then get buyer insights in a single workflow.

Call GET /api/v1/address-info-v2 to get lead property details, then verify the result

AI Agent Integration via Jentic

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

Search Jentic for 'get lead property details', load the operation schema, and execute with Jentic-managed credentials

Key Endpoints

14 endpoints — welcome to the quantiv api documentation! the quantiv api empowers developers with seamless access to powerful data-driven solutions.

METHOD

PATH

DESCRIPTION

GET

/api/v1/address-info

Get Lead Property Details

GET

/api/v1/address-info-v2

Get Lead Property Details

GET

/api/v1/buyer-insights

Get Buyer Insights

GET

/api/v1/roof-estimate

Get Lead Value - Roof

GET

/api/v1/gosolar-index

Get GoSolar Index

GET

/api/v1/utility-bill

Get Utility Bill Information

POST

/api/v1/roof-estimate-widget

Create EngagePro™ - Lead Widget

GET

/api/v1/roof-estimate-widget/{referenceId}

Retrieve EngagePro™ - Lead Widget

GET

/api/v1/address-info

Get Lead Property Details

GET

/api/v1/address-info-v2

Get Lead Property Details

GET

/api/v1/buyer-insights

Get Buyer Insights

GET

/api/v1/roof-estimate

Get Lead Value - Roof

GET

/api/v1/gosolar-index

Get GoSolar Index

GET

/api/v1/utility-bill

Get Utility Bill Information

POST

/api/v1/roof-estimate-widget

Create EngagePro™ - Lead Widget

GET

/api/v1/roof-estimate-widget/{referenceId}

Retrieve EngagePro™ - Lead Widget

Why Jentic?

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

Setup

Wiring the Quantiv API by hand means shaping each query to public-api.quantiv.io and handling the address, roof, and utility responses yourself. Through Jentic you install once, import the Quantiv API from the API Directory, and your agent calls it.

Permission scoping

The Quantiv API is read-oriented and works through operations like address-info and roof-estimate rather than a resource id you own in the path, so scope by operations: limit the agent to the operations it needs, such as fetching property details. You choose which operations are in that set, and the agent can call only those.

Credential isolation

Any Quantiv connection details are stored once, encrypted, by your own Jentic One instance and injected at execution time. They never enter the agent's prompt, logs, or context.

Intent-based discovery

Agents search Jentic by intent such as 'get property details for an address' or 'estimate a roof', and Jentic returns the matching Quantiv operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

FAQs

Specific to using Quantiv API through Jentic.

What authentication does the Quantiv API use?

The Quantiv API uses no 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 get lead property details with the Quantiv API?

Yes. Use the GET /api/v1/address-info endpoint. The API returns structured JSON responses that agents can parse and act on directly.

What are the rate limits for the Quantiv 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 get lead property details through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'get lead property details'. Jentic returns the matching Quantiv API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

How many endpoints does the Quantiv API have?

The Quantiv API exposes 14 endpoints covering lead append level 1, lead append level 2, buyer insights operations.

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

Yes. Because you run Jentic One yourself, your own rules decide which Quantiv operations the agent may call and which connection details it may use. The Quantiv API is read-oriented and works through operations like address-info, address-info-v2, buyer-insights, roof-estimate, and gosolar-index rather than a resource you own in the path, so you scope by operation: allow only the ones the agent needs, such as fetching property details, and it can call nothing else.

Quantiv API

AI ReadinessFoundational (C)55/100

See full scorecard

Official vendor OpenAPI document · agent-readyAnalyticsData Pipelinesnone14 EndpointsREST

For Agents

Programmatically get lead property details, get lead property details. Covers 14 operations.

Use for: I need to lead property details, I want to lead property details, Search for buyer insights, Find all lead value - roof

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

Welcome to the Quantiv API documentation! The Quantiv API empowers developers with seamless access to powerful data-driven solutions. Our suite of APIs enables you to efficiently interact with key resources, automate processes, and enhance your applications with reliable insights. Whether you're integrating property intelligence, optimizing lead quality assessments, or leveraging advanced data ana. The API exposes 14 endpoints.

Jentic One on Github View OpenAPI Document

Show dimension breakdown

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: A-Signals: 4

88%

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

100%

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: ASignals: 4

62%

Example Density

How richly the API is illustrated with examples.

100%

Example Validity

Percentage of examples that conform to their schemas.

75%

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: FSignals: 4

47%

Description Coverage

Coverage of descriptions across API elements.

Error Standardization

Coverage of RFC 9457 Problem Details for error responses.

OperationId Quality

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

56%

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.

100

Security

Trust, risk posture, and security compliance.

Grade: A+Signals: 1

100%

Authentication Strength

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

100

AI Discoverability

Findability, semantic richness, and reasoning readiness.

Grade: A+Signals: 1

100%

Descriptive Richness

Clarity and depth of descriptions across API elements.

Connect the Quantiv API to your agent

Capabilities

Use Cases

Start building with Quantiv API

Key Endpoints

Why Jentic?

Related APIs

FAQs

Quantiv API

Jentic AI Readiness Score

Quantiv 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