Most automotive software is built to keep you in, not to let you build.
Closed formats. Undocumented exports. Integrations that require a sales call and a six-month roadmap promise. That's been the default for decades, and everyone in the industry has quietly accepted it as the cost of doing business.
We're betting against it.
Here's the bet, stated plainly: the next decade of European automotive software gets built on open, versioned APIs - not on lock-in.
So that's what we're shipping. Versioned REST with a public OpenAPI spec, so anyone can read the contract before they write a line of code. An MCP layer, so AI agents can work with vehicle data as a first-class citizen instead of scraping a UI. And a marketplace, so the integrations a dealer actually needs don't depend on us building every one ourselves.
Why now? Two reasons.
The EU Data Act is shifting the ground under closed systems - data access is becoming a right, not a favour. And AI changes who the "user" of a platform is. Half your future integrations won't be people clicking buttons. They'll be agents calling endpoints.
The walled garden was a fine strategy when switching was hard and software was slow. Both of those are no longer true.
We'd rather compete on being the best place to build, not the hardest place to leave.
If you're building anything that touches a vehicle - valuation, inventory, workshops, financing - the VehIQ API is open by design. Come kick the tyres. I read every message.
What would you build first?
#automotive #openapi #buildinpublic