Custom builds

Your systems, wired into your site and your AI.

When your store needs something Driverseat doesn't do yet, the people who build Driverseat build it with you: an MCP server for your own systems, a vendor we don't connect to yet, or a one-off tool on your data. Quoted per project.

Four builds, each drawn as a lane from something your store has, through Driverseat, to where it shows up. The first is built for a dealer group: when a shopper asks whether a car is still available, the site assistant asks the group's own MCP server with one tool, check_availability, and keeps only two fields from the answer, whether the car is available and its status. A check that fails is never read as the car being sold. The other three are examples of what we would build: your own systems next to the Driverseat connector in Claude, ChatGPT or Codex; a vendor built in as an integration; and a small tool on the dealership API.

Built for a dealer group

Is this one still available?

What a build connects

04 · The answer comes from the dealer's own systems, not only the website feed

01 · How it works

You see the scope and the price before we build.

A call first, then a written scope and a quote. The people who build Driverseat build it, and it runs on Driverseat once it's live. Every build is quoted per project.

You tell us the job and the systems involved. If Driverseat already does it, we say so.

Written scope

Example

Real vehicle availability in the site assistant

Written up from the build for a dealer group with its own MCP server.

The ask
When a shopper asks if a car is still there, answer from our own systems, not only the website listing.
What you have
An MCP server of your own, in front of your DMS and CRM.
What we connect
One tool on your server, check_availability, and only for a car your site already lists.
What comes back
Two fields, available and status. Price, fees and everything else in the answer are dropped; Driverseat stays the source for price.
When it can't answer
No answer in 10 seconds, or a car it can't find, counts as no answer. The assistant never tells a shopper a car is sold on that.
Quote
Quoted per projectAgreed before any work starts
How it's built
Beside the site assistant's own tools, with its own tests. Your server's tool names and text never reach the model.
Once it's live
Off until your credentials are in place. Every check is recorded, and a failed check never stops the chat.

02 · Starts from

Most of a build already runs.

A build starts from pieces that run on Driverseat today, so we only add the part your store is missing.

  • › Which cars are on hold?
    dealership_accounts
    graphql_schema
    graphql_query
    graphql_mutation_propose
    agent_action_decide
    Changes wait for you

    The AI connectorPilot

    Claude, ChatGPT and Codex read your stores with your access, and every change waits for your approval.

    Connector docs
  • GET /v1/vehicles?condition=NEWx-api-key: sk-driverseat-…
    { "data": [ … ] }
    leadvehiclepageinquirytrade in+8 more

    The dealership APIToday

    Read-only access to 13 kinds of record, from leads to pages, plus replacing a car's photos by VIN.

    API docs
  • Yours

    48 integrations

    Chat, trade-in, finance, tracking and consent vendors, each set up from one settings page.

    See the integrations
  • Copy HTMLWebsite providerStandardDealerOn
    Widens the DealerOn content area so this page uses its original spacing.

    Copy HTML

    For a store whose site runs on another provider: a finished page as one block of HTML, with a DealerOn mode.

    How it works

Tell us what your store needs.

If Driverseat already does it, we'll show you where. If it doesn't, you get a written scope and a quote before anything is built.