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.

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

Yes. Because you run Jentic One yourself, your own rules decide which DealerAI operations the agent may call and which credentials it may use, so you can allow read-only conversation and VIN lookups while withholding writes like POST /ailm/contact, POST /ailm/engage, or the inventory feed uploads. Since DealerAI puts the vehicle identifier in the URL path at GET /inventory/vehicle/{vin}, a rule can pin the agent to a single vehicle for reads. Contact engagement or inventory posting are included only if you add them.