Install Jentic One Beta

Connect the DealerAI API to your agent

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

Look up new and used vehicle inventory, or fetch a single vehicle by its VIN

Capture a showroom lead by creating or updating a contact record

Queue an outbound engagement for a contact in one call

Retrieve past customer conversations to give an assistant context

Upload new and used vehicle inventory to keep dealership listings current

GET STARTED

Start building with DealerAI API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use DealerAI API for, with concrete tasks.

★ AI Sales Assistant for a Dealership

An AI assistant answers buyer questions on the lot or website by reading live inventory and capturing the lead in the same session. It looks up new and used vehicles, fetches a specific car by VIN, and creates a contact so the sales team can follow up. Through Jentic the agent discovers these operations by intent and calls them without hand-wiring the API.

Look up used inventory for a Honda Civic, then create a contact for the interested buyer with their name and phone number

Vehicle Inventory Lookup

Retrieve current new and used vehicle inventory for a dealership, or pull the full record for one vehicle by its VIN. This backs shopping tools, price checks, and availability answers without scraping the dealer website, and keeps responses grounded in what is actually on the lot.

Fetch the vehicle record for VIN 1HGCM82633A004352 and report its availability

Lead Capture and Engagement

Turn an inbound inquiry into a tracked contact and a queued follow-up. The agent creates or updates the contact, then queues an engagement so the dealership reaches out, and can read prior conversations to avoid repeating questions. This keeps lead handling consistent across chat, web, and phone channels.

Create a contact for a walk-in prospect and queue an engagement to schedule a test drive

Key Endpoints

8 endpoints — the dealerai api manages customer contacts and outbound engagements for automotive dealerships and looks up new and used vehicle inventory, including an individual vehicle by its vin.

METHOD

PATH

DESCRIPTION

POST

/ailm/contact

Create or update a contact

POST

/ailm/engage

Create a contact and queue an engagement

GET

/conversations

Retrieve customer conversations

GET

/inventory/new

List new vehicle inventory

GET

/inventory/vehicle/{vin}

Get a vehicle by VIN

POST

/ailm/contact

Create or update a contact

POST

/ailm/engage

Create a contact and queue an engagement

GET

/conversations

Retrieve customer conversations

GET

/inventory/new

List new vehicle inventory

GET

/inventory/vehicle/{vin}

Get a vehicle by VIN

Why Jentic?

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

Setup

Wiring the DealerAI API by hand means setting up HTTP basic authentication and handling its inventory and contact endpoints yourself. Through Jentic you install once, import DealerAI from the API Directory, store the credential once, and your agent calls it.

Permission scoping

DealerAI carries the contact and engagement details in the request body, so rules bound which operations your agent may call, not which contact it touches. You choose the operations it may call, so write operations like uploading inventory are not included unless you add them.

Credential isolation

Your DealerAI credentials 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 'look up used car inventory' or 'create a dealership contact', and Jentic returns the matching DealerAI operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

FAQs

Specific to using DealerAI API through Jentic.

What authentication does the DealerAI API use?

The DealerAI API authenticates with HTTP basic authentication using your API credentials, per its OpenAPI spec. Through Jentic the credentials are stored encrypted by your own Jentic One instance and injected at call time, so they never sit in the agent's prompt or logs.

Can I look up a vehicle by VIN with the DealerAI API?

Yes. A GET request to /inventory/vehicle/{vin} returns the record for a single vehicle, and separate operations list all new and used inventory. An agent can use these to answer availability and price questions grounded in the dealership's current stock.

What are the rate limits for the DealerAI API?

The OpenAPI spec does not specify rate limits. Check the DealerAI developer documentation at https://api.dealerai.com/api-docs/ for current limits before running high-volume inventory syncs.

Is there a DealerAI MCP server?

You don't need an MCP server to give your agent the DealerAI API. Jentic connects it directly from the API Directory: import it, store your credential once, and your agent calls the inventory and contact operations it needs.

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

Yes. Write a rule that allows only the inventory-read and contact-create operations, so the agent can look up vehicles and capture leads but cannot upload inventory or read conversation history, and every call it makes is logged.

How do I capture a lead with the DealerAI API through Jentic?

Search Jentic for 'create a dealership contact', and it returns the POST /ailm/contact operation with its input schema so your agent submits the lead directly. To run it on your own infrastructure, install Jentic One from its GitHub repo.

DealerAI API

AI ReadinessFoundational (D-)40/100

See full scorecard

Official vendor OpenAPI document · agent-readyCRMContact Managementbasic8 EndpointsREST

For Agents

Look up new and used vehicle inventory, capture showroom leads, and queue customer engagements for an automotive dealership. Retrieves past conversations so an agent can respond with context.

Use for: Find all new vehicles currently in inventory, Look up a used car by its VIN, I need to create a contact for a showroom walk-in, Queue a follow-up engagement for a prospective buyer

Not supported: Does not handle financing, payment processing, or service scheduling. Use for dealership contact and vehicle inventory management only.

The DealerAI API manages customer contacts and outbound engagements for automotive dealerships and looks up new and used vehicle inventory, including an individual vehicle by its VIN. It captures showroom leads by creating or updating a contact, queues a follow-up engagement in a single call, and retrieves past customer conversations so an assistant can respond with context.

Jentic One on Github View OpenAPI Document

Show dimension breakdown

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: ASignals: 4

99%

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

60%

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

34%

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.

57%

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

10%

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 DealerAI API to your agent

Capabilities

Start building with DealerAI API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

DealerAI API

Jentic AI Readiness Score

DealerAI 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