pitch.auto.dev
The automotive default.
↓ scroll · arrow keys
The primary caller is an agent acting for a dealer or a developer, so this deck opens the way an agent would read it: capabilities, protocol, rates. The story comes after the contract.
| verb | capability |
|---|---|
| decode | A VIN into year, make, model, trim and build data. |
| search | Live retail listings, by anything a buyer or an agent would filter on. |
| specs | Vehicle specs and photos for a decoded vehicle. |
| value | A vehicle against the retail market. |
| transact | The deal, buyer, financing, trade and payoff objects a car sale actually needs. |
The first four are data reads, live on the public card today. The fifth's exposure as self-serve metered endpoints is being staged deliberately, because a transaction endpoint that touches titling or F&I crosses into functions a statute reserves for licensed people, and we do not publish an endpoint that implies otherwise.
transact runs in production underneath Vin: vin.company is the consumer retail experience running on these rails, and the deal flow a visitor walks through there is the fifth verb at work.
auto.dev serves. The API, the documentation and the rate card are public on the domain — no sales call between a developer and a working key.
mcp.auto.dev ships an MCP server exposing these rails as tools, with an agent skill that auto-configures it for the major agent environments. An agent working an automotive problem gets configured by the skill rather than by a human reading setup docs.
Transaction endpoints on the public self-serve card, with the licensed-function boundary stated on each endpoint.
One posted card, metered per call, the same card for everyone. No enterprise dark pricing: a price an agent cannot read is a price an agent cannot pay, and agents are the primary caller. No seats, because agents do not have seats — the unit is the call and the meter is the contract.
List price IS the arm's-length price — by design. The card is the same for Vin — the other brand of this same company — as for any third party: one public price, no internal discount, nothing an accountant has to construct.
Third parties paying the posted rate are what will make the internal transfer price a market price rather than an accounting position. The external/internal split that proves it posts behind the gate, alongside the revenue metric on the proof slide.
The live card, with the actual figures, is on the domain. This deck states the model; the domain states the prices.
Our agents ran sales, BDC and desking on rocketauto.com for about a year — the archived capture shows the national marketplace as it ran. What was not unstaffed — the dealer licence, titling, DMV processing and F&I compliance — stayed with Rocket's licensed humans, and those humans were Rocket's, not ours.
rocketauto.com now redirects to a corporate index page. That borrowed-supply split is the story: when the relationship ended, a working business stopped, because its regulated supply was borrowed.
vin.company returns 200. The capability outlived the host it first ran under, and it came back as Vin — on these rails.
And the supply changed. The regulated supply that was borrowed then is contracted now: the licensed statutory functions on each transaction run through licensed partners under our own agreements, with the boundary stated on every transaction. The designed end-state — a dealer-of-record layer inside an entity the company can own, cloud.motors.vin — flips this claim when it cuts over to production.
What publishes here: the revenue window, the base, and the external/internal
split — all three together, as <Placeholder name="arr-external-split" gate="stack#1 §A5" />,
when the numbers workstream settles them behind stack#1 §A5.
Primary motion is B2A2D — our agent serves the deputized developer, who builds for the dealer market. Secondary is B2A2B, where a dealer's own business system calls the rails directly. In both, the agent hop is the channel: discovery, evaluation, purchase and use are machine steps, which is why the contract above leads the deck.
The ratified route matrix reads B2A2D with D = Developer (deputized), while auto.dev has elsewhere been described as a "B2D" motion with dealers as the customer. The record (brand.mdx) uses the ratified reading — developer as D, dealers as the business the developer serves — and the canon tension stays flagged rather than quietly overloading the letter.
Costs are mostly fixed, so the marginal cost of the next tenant is near zero and blended margin rises with volume. Functions migrate Human → Agentic → Generative → Code, and each migration is structural margin expansion rather than an efficiency programme.
The floor is regulatory, per vertical — and automotive's data plane has a low one: most of what auto.dev does can be Code. The transaction layer's floor is real but thin, and it is priced as a floor, not wished away.
If agents are the buyers, being discoverable and callable by an agent is the distribution channel — what SEO and a sales team were for SaaS. The moat is the position: automotive resolves to auto.dev in the agent-discovery layer, the way a domain resolves to its nameservers.
api.qa and the Agent eXperience Protocol are how that position is held rather than merely occupied: conformance is measured, published and re-run, so "the default" is a verified property instead of a marketing claim.
The namespace position is occupied: auto.dev serves the industry's exact-match developer name, with card, docs and MCP tools on the open domain.
AXP conformance is a design target, not a verified state. No conformance run has been published; the claim flips when the cold re-run URL is live.
One entity — Drivly, Inc. — carrying two brands: auto.dev and vin.company.
auto.dev and Vin are two brands of one company. auto.dev is the rails, sold to dealers and the developers who build for them; Vin is the consumer retail experience built on those rails, and the card is the same for Vin as for any third party. Two ICPs, two records, one entity — each record references the other, and neither restates the other's terms.
Point your agent at auto.dev.
Everything load-bearing in this deck is public: the card, the docs, the tools, and the claim states — green is verified, amber is pending and says so. Forward it whole.