DealerAI API

Name: DealerAI API API
Brand: DealerAI API
Availability: InStock

✓ Official Vendor SpecCRMContact Managementbasic8 EndpointsREST

For Agents

Push dealership leads and inventory into DealerAI, trigger AI engagement on a contact, and read back the resulting conversations or look up a vehicle by VIN.

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.

Install Jentic One Beta (Self-Hosted)

Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | 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 API.

Create or update a dealership contact without sending a message via /ailm/contact

Queue an AI-driven engagement against a contact through /ailm/engage

Retrieve conversation transcripts produced by the DealerAI assistant

Upload new vehicle inventory and refresh used vehicle inventory feeds

GET STARTED

Start building with DealerAI API API

Explore with Jentic

View OpenAPI Document

DealerAI is an AI assistant platform for automotive dealerships, exposing a focused v1 API that covers contact ingestion, conversational engagement, and vehicle inventory feeds. The 8 endpoints split between an AI lead-management surface (/ailm/contact, /ailm/engage), a conversation log reader, and inventory operations for new and used vehicles, including a VIN-keyed lookup. Authentication is HTTP Basic, and the API is designed to be called from dealership management systems pushing inventory and lead events into DealerAI's chat workflows.

Use Cases

Patterns agents use DealerAI API API for, with concrete tasks.

★ DMS-to-DealerAI lead sync

Dealerships running a CRM or DMS need leads to land in DealerAI so the AI assistant can follow up. POST /ailm/contact creates or updates the contact silently, while POST /ailm/engage takes the same identifier and queues an outbound engagement. Splitting the two operations lets a workflow seed contacts in bulk overnight and engage selectively the next morning.

POST /ailm/contact with the lead payload, then POST /ailm/engage with the same contact identifier to start the AI follow-up.

Inventory feed maintenance

DealerAI's responses depend on accurate vehicle data. POST /inventory/new and POST /inventory/used push fresh feeds, while the corresponding GETs let an agent reconcile what DealerAI currently holds against the source of truth. /inventory/vehicle/{vin} is the single-VIN lookup used to confirm a specific car is live before pointing a customer at it.

POST /inventory/used with the day's used-car feed, then GET /inventory/vehicle/{vin} for any VIN that should be highlighted to a customer.

Conversation review and quality monitoring

Sales managers want visibility into how the AI assistant is handling leads. GET /conversations returns the recent conversation log so a workflow can pull transcripts, score them, and surface low-quality or stalled threads to a human BDC rep. This is also useful for building an offline analytics store of dealership AI interactions.

GET /conversations with a date filter and forward any thread without a human reply in 24 hours to a sales manager.

AI agent orchestrating dealership outreach via Jentic

An agent embedded in a dealership workflow can use Jentic to discover DealerAI's contact and engage endpoints, ingest a lead from a website form, and trigger AI follow-up — all without exposing the HTTP Basic credentials. The agent can then poll /conversations to confirm the lead was engaged and escalate if not.

Search Jentic for 'engage a DealerAI contact', execute /ailm/engage with the new lead, then GET /conversations to confirm the engagement started.

Key Endpoints

8 endpoints — dealerai is an ai assistant platform for automotive dealerships, exposing a focused v1 api that covers contact ingestion, conversational engagement, and vehicle inventory feeds.

METHOD

PATH

DESCRIPTION

POST

/ailm/contact

Create or update a dealership contact

POST

/ailm/engage

Queue an AI engagement for a contact

GET

/conversations

Retrieve AI conversation transcripts

POST

/inventory/new

Upload new vehicle inventory

POST

/inventory/used

Upload used vehicle inventory

GET

/inventory/vehicle/{vin}

Look up a vehicle by VIN

POST

/ailm/contact

Create or update a dealership contact

POST

/ailm/engage

Queue an AI engagement for a contact

GET

/conversations

Retrieve AI conversation transcripts

POST

/inventory/new

Upload new vehicle inventory

POST

/inventory/used

Upload used vehicle inventory

Why though Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

DealerAI HTTP Basic credentials are stored encrypted in the Jentic vault (MAXsystem). Agents execute operations through Jentic and the Authorization header is built at call time — the raw username and password never enter the agent's context.

Intent-based discovery

Agents search Jentic by intent (e.g., 'engage a DealerAI contact' or 'upload used vehicle inventory') and receive the matching operation with its input schema, sparing the agent from learning DealerAI's /ailm and /inventory path conventions.

Time to first call

Direct DealerAI integration: 1-2 days to wire up Basic auth, the two-step contact-then-engage flow, and inventory feed scheduling. Through Jentic: under an hour — search, load, execute.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Complementary

Edmunds API

Vehicle reference data, pricing, and specifications for automotive workflows.

Use alongside DealerAI when you need MSRP, true cost to own, or trim-level details that the dealership feed does not carry.

Alternative

Salesforce API

General-purpose CRM widely used in automotive groups for centralised lead management.

Choose Salesforce when leads must live in a dealer-group CRM rather than DealerAI's AI engagement layer.

Complementary

HubSpot CRM Contacts

Marketing-led CRM that pairs with dealership tools for nurture sequences.

Pair with DealerAI when marketing automation lives in HubSpot but conversational engagement runs in DealerAI.

FAQs

Specific to using DealerAI API API through Jentic.

What authentication does the DealerAI API use?

DealerAI uses HTTP Basic authentication on every endpoint. Through Jentic the username and password are held in the encrypted vault and applied at execution time, so the raw credentials never enter the agent's context.

Can I create a lead in DealerAI without triggering an AI message?

Yes. POST /ailm/contact creates or updates the contact silently. Use /ailm/engage as a separate call when you want the AI assistant to actually reach out, which lets you batch-import leads first and engage selectively.

How do I look up a specific vehicle in DealerAI?

Call GET /inventory/vehicle/{vin} with the 17-character VIN. The response confirms whether the vehicle is in the current dealership feed and returns its stored attributes. Use this before pointing a customer at a specific car.

What are the rate limits for the DealerAI API?

The OpenAPI spec does not document explicit rate limits. Treat the inventory POSTs as bulk operations — push a full feed once per scheduling window rather than per-vehicle to keep request volume reasonable.

How do I push a lead and trigger AI follow-up through Jentic?

Run pip install jentic, search for 'engage a DealerAI contact', and Jentic returns the /ailm/engage operation with its input schema. Load it, supply the contact identifier and engagement payload, and execute. Pair with /ailm/contact first if the lead is new.

Does DealerAI handle finance, F&I, or service appointment booking?

No. The v1 API is scoped to lead engagement, conversation logs, and inventory feeds. There are no endpoints for finance applications, deal jackets, or service scheduling — pair with a DMS or service-scheduling API for those.