API access denied
Your tools can automate anything. Except your own website.
Dealerships and the builders who serve them are locked out of their own site—no API, no publishing automation, no choice. Bring API, MCP, Claude Code, Codex, or Hrizn. We're demanding open access: your data, your tools, your call.
// join dealers, GMs, marketers, agencies & builders
API ACCESS DENIED
PUBLISHING AUTOMATION BLOCKED
> connection refused_
Open website backends
Open integrations for dealers
Open access for agencies
The absurdity
Everyone else learned to relax and open up.
Don't worry—it'll be OK!
Open the website backend and let dealers plug in.
Every other tech surface in a dealership has an API at this point—from the DMS to the CRM to the CDP. Integrators plug in every day. But the website, the customer-facing hub for inventory, specials, blogs, and brand story, is still a walled garden. No standard backend access, no real integration lane for the tools dealers already run.
Forcing dealers and their agencies to log in manually, update content by hand, replace specials, add new vehicle comparisons, and even publish simple blogs is out of touch with the modern world—and the pace it actually runs at. AI-powered automations are already improving workflow and process across the rest of the stack. The dealership website platform cannot remain the bottleneck.
200
DMS · CRM · CDP integrations
200
agents + AI on connected stacks
403
website backend access
403
dealership.waiting.on.vendor
202
manual login · specials · blogs
// DMS · CRM · CDP: integrated · website: walled garden
Backend access denied
We just want a backend integration.What's the big deal?
Specials expire. Blogs are ready. Vehicle comparisons need to go live while shoppers are still comparing. Instead, dealers and agencies are pushed back into the CMS—manual logins, manual updates, click-through publishing—on the one platform that still won't open up for the backend integrations the rest of the dealership stack already has.
// POST /api/pages — 403 · your CRM has an API; your website doesn't
Sign the petition and spread the word!
Share on LinkedInBackend integrations
Plug in. Publish.
Open the website backend and let dealers plug in.
Dealers and builders should connect to the website backend and automate publishing—through API, MCP, Claude Code, Codex, or Hrizn. Any tool you trust. Not one vendor. Not one backdoor negotiation per rooftop.
// bring your own stack
The demand
Ten open-access standards every provider must ship
The website should integrate like every other system on the lot—not trap dealers in manual CMS work while the rest of the stack runs on APIs and automation. Not unrestricted access — modern, controlled, auditable access using standard safeguards.
01
API access as a core feature
// enterprise-only contracts
Standard, included — not an enterprise upsell or extra access fee.
02
Control your own content
// your pages, their gatekeeper
Create, update, publish, schedule, and delete the pages, specials, media, and metadata you own—without forcing every rooftop and agency through manual CMS logins for routine work.
03
Authorized third-party access
// Hrizn isn’t the problem — “approved vendors only” is
Grant the employees, agencies, and tools you choose — even ones that compete with the provider.
04
Complete, usable docs
// private GitHub ≠ open API
Auth, fields, examples, errors, rate limits. An undocumented API is not an open program.
05
Equitable access
// one rooftop ≠ one integration lane
The same core capabilities for one rooftop as for a 500-store public group.
06
Modern integration support
// MCP in the deck, 403 in production
APIs, webhooks, structured content, OAuth, and AI / MCP-enabled systems.
07
No punitive integration fees
// paywalling your own content
Don’t charge dealers to touch content they already pay for and created.
08
Content portability
// can’t leave if you can’t extract
Export pages, copy, media, and structured content in a usable format.
09
Transparent audit controls
// who plugged in, when
See who and what has access, what changed, when — and revoke instantly.
10
A public timeline
// “roadmap” is not a shipped API
State plainly what exists today, who’s eligible, what it costs, and when full access ships.
A note from Hrizn
We'd rather integrate than replace. This isn't about Hrizn — it's about your right to choose.
If open access doesn't arrive, the market will route around closed platforms — and we're more than capable of helping it. Walled-garden website backends are absurd; we'd simply prefer to build with the platforms dealers already run.
The Hrizn Team
Add your name
Sign the demand
Every signature tells providers the standard has to change—backend access should not require a Fortune 500 badge. Public on the wall, or anonymous — your call.
Under a minute — no login.
Email stays private; only first name, last initial, dealership & website show.
Anonymous still counts toward the total.
The signatories
The wall of builders
Be the first to sign
Names appear here the moment people sign (unless they choose to stay anonymous).
Live wall
// dealers · GMs · marketers
// agencies · integrators · builders
// POST /sign — no ticket required
GET /petition/signatures — streaming
200 OK
Website vendors
Have an Open API for your platform? Share it with the world.
Let us know and be featured on the Provider hall of fame.
Looking to partner with Hrizn for a deeper generative content experience? Let us know in the same form — we read every submission.
Provider hall of fame
Loading hall of fame…
Open the website backend.
Let dealers plug in.
Every other dealership system has an API. The customer-facing website shouldn't be the walled garden.
Sign the demand →