BuilderXP

Build What Your Dealership Needs

The Builder Expansion Pack (BuilderXP) is a solution that enables dealers to build their own tools, reporting, applications, and workflows to complement Lightyear’s Enterprise Retail Cloud DMS. It gives you real-time access to read and write to your dealership’s DMS through APIs and Governed MCP.

“DealerBuilt being founded by dealers and driven by dealer insights has moved to a whole new level by empowering our dealers to build their own solutions.”
— Dave Apseloff, Director of Strategic Accounts

How BuilderXP works

BuilderXP solutions:

  • BuilderXP:Read and write access to your production database, through APIs for your solutions and Governed MCP for the AI assistants your users work with
  • Test Site: Highly recommended option for copy of your Lightyear Enterprise Retail Cloud user interface, configurations, data (snapshot), and data anonymization
  • Test Site refresh: Option to refresh the data (snapshot) and anonymize

Lightyear data flows in near real-time to a replication database secured in a DealerBuilt AWS environment, your solution reads it through direct access to PostgreSQL and/or read-only access API, then your solution writes back to Lightyear’s production database through a write access API token per use case.

Why use BuilderXP?

Dealers can build AI communication tools that work with BuilderXP to help their dealerships become more efficient and their Lightyear Enterprise Retail Cloud DMS more effective.

Foundational strengths include:

  • Enterprise-grade accounting across the entire dealership group – to drive standards
  • Single name file across the entire dealership group – for one unified customer record
  • Single vehicle file and single parts file across the entire dealership group, by location – for group-wide and store insights
  • Modern APIs – with robust breadth and depth of data elements
  • Advanced Access to data – Direct access to PostgreSQL database for read access for high volume/high cadence and a modern API for read/write for normal use
  • Enterprise-grade security

BuilderXP is strictly for use with internally built solutions and not for data exchanges with automotive third-party vendors selling to other dealers. This, of course, excludes your AI assistant, such as Claude or ChatGPT, which are vendors you subscribe to separately to plug into the Governed MCP. DealerBuilt has numerous third-party vendors today in the Certified Partner Program and is open to adding more based on dealer requirements. Vist the Certified Partners page for information regarding third-party vendors.

Builder’s Wall

Dealers are already building. Here’s what they’ve built.

Hear it from the builders:

Security and your data

Security

BuilderXP is designed so that you are in control to who has access to ensure what they build does not impact the speed of the production database for your employees.

  • API: Each use case receives a token.  Access is limited to your approved networks.  Credentials are shared through secure, one-time links.  Tokens can be independently suspended, rotated, or revoked.
  • Governed MCP: Each user signs in as themselves with multi-factor authentication.  Access follows the user security you control.  You choose which AI products and which users are enabled.  Every request is logged.

Who’s responsible for what

DealerBuilt protects your data inside DealerBuilt systems. Once data moves into your own solutions or to the AI provider you choose, your dealership is responsible for keeping it secure.

BuilderXP is strictly for use with internally built solutions and not for data exchanges with automotive third-party vendors selling to other dealers. This of course excludes your AI assistant, such as Claude or ChatGPT, which are vendors you subscribe to separately to plug into the Governed MCP. DealerBuilt has numerous third-party vendors today in the Certified Partner Program and is open to adding more based on dealer requirements. Vist the Certified Partners page for information regarding third-party vendors.

Read the BuilderXP Product Terms

How to Get Started with BuilderXP

1

Meet

Discuss your use cases, your solution(s), our tools, and the pricing.

2

Sign Up

Sign the Order, submit answers to a questionnaire for each use case where you name the solution, define the problem you are solving, add the APIs and MCP user access you expect to need, and share the benefit it will have.

3

Kickoff

DealerBuilt will review the implementation logistics, collaborate on your use case and access needs, discuss the tools that best suit your use cases, and request API tokens and MCP user access by use case. From initial order to Go Live is approximately three weeks, assuming a promptly scheduled kickoff.

4

Build

You can build before, during, or after your Go Live date.

Governed MCP is in pilot and will roll out by data area.

What’s next for your dealership?

Ready to start building?

See how Lightyear and BuilderXP give your dealership a solid foundation and enable you to build your own solutions.

Learn About Lightyear and BuilderXP

Already building?

If you need to adjust your API token access, request a new API token for a new use case, or adjust your MCP User Access, just let us know.

Submit New Use Case

BuilderXP FAQs

Does DealerBuilt have an API?

Yes. BuilderXP is strictly for use with internally built solutions and not for data exchanges with third-party vendors. DealerBuilt has numerous third-party vendors today in the Certified Partner Program and is open to adding more based on dealer requirements. Visit the Certified Partners page for information regarding third-party vendors.

What is an API?

An API (Application Programming Interface) allows read and/or write access to share data between two different software solutions

What is a Governed MCP?

A governed MCP (Model Context Protocol) is an enterprise deployment of the Model Context Protocol that enforces strict policies, identity verification, scope limits, and audit logging before AI assistants can access or execute backend tools and data

Can I connect AI tools to my DMS?

Yes. Depending on the use case, API and/or Governed MCP is built for exactly that. For your solutions that runs without a signed-in user, they utilize APIs with via a token. For an AI assistant for your employees to utilize, such as Claude or Chat GPT, you purchase that solution and your admin makes it available. Then, your employee signs in and connects to that assistant, and the assistant has the same permissions as the employee.

If it’s our data, why is there a cost?

The data you enter into our system is yours. The BuilderXP fee and options cover our infrastructure, API platform, security, maintenance, and the team that supports you as you build your own solutions. Data we license from OEMs and vendors may have usage restrictions, because that data is theirs.

How much does BuilderXP cost?

BuilderXP has a monthly fee per store within a database. A Test Site is optional but highly recommended, for an additional monthly fee per database. A one-time refresh to pull in new Test Site data and anonymize it is also available. There’s no setup fee, because your team needs to be experienced with these tools to use them. Contact us to discuss the solution, pricing and options.

Who builds the solution?

You do, with your in-house team or an outside IT partner working on your behalf.

How long does setup take?

Typically, about three weeks from signature to Go Live.

Is BuilderXP secure?

Every solution gets its own API token. Access is limited to what you grant your team and to your approved networks, and DealerBuilt monitors usage. Governed MCP access follows the user security you control. Once data leaves DealerBuilt systems, your dealership is responsible for protecting it. See the BuilderXP Product Terms for details.

Is BuilderXP the same as an open DMS?

BuilderXP is one part of what makes Lightyear the most open DMS in the industry. Lightyear Enterprise Retail Cloud gives dealers several ways to access their data:

  • Standard reporting, included with Lightyear
  • Custom reporting, for a one-time programming fee
  • Business Intelligence, with advanced dashboards and reporting
  • The Certified Partner Program, for third-party vendor integrations
  • BuilderXP, with read and write access through APIs and Governed MCP

“Open” doesn’t mean “free,” though. BuilderXP is a paid service that covers the infrastructure, tools, security and team you need to build with your data.

Can a third-party vendor use BuilderXP to serve multiple dealers?

BuilderXP is strictly for use with internally built solutions and not for data exchanges with automotive third-party vendors selling to other dealers. This of course excludes your AI assistant, such as Claude or ChatGPT, which are vendors you subscribe to separately to plug into the Governed MCP.  DealerBuilt has numerous third-party vendors today in the Certified Partner Program and is open to adding more based on dealer requirements. Vist the Certified Partners for information regarding third-party vendors.