BayLink connects AV fleet operators to the long tail of independent service providers and settles every work order automatically. Capped up front, released the moment the vehicle returns.
Onboard a provider in a day, not a quarter. Rails, not real estate.
LIDAR calibration and sensor work the integrated players won't staff for.
No depots to own. Every new operator and shop is additive, not capital.
BayLink doesn't compete with the operators or the shops. It connects them.
The envelope is the unit of work and the unit of settlement. It carries the service request, the price cap, the stage, and the transfer. One object, auditable end to end.
Operator dispatches a request. BayLink opens an envelope and locks a price ceiling in cents.
/confirm-appointmentThe provider completes the work. Stages move dispatched → scheduled → in-bay → returned, live.
/rotation-returnedWhen the vehicle returns, the actual amount is released against the cap, never over.
/close-invoiceFunds transfer to the provider on Stripe Connect. Reconciliation is the byproduct.
Stripe ConnectBayLink expresses work and settlement in standards your systems already speak. Integrate once; the rails handle the rest.
Each envelope is an ACP transaction. Service requests, price caps, and settlement intent travel as structured payloads in automotive's modern commerce standard. It's the move past legacy lead formats, extended for fleet servicing.
ACP is published as an open specification under Apache 2.0, with a conformance suite anyone can run. Every BayLink envelope validates against it, so there's no proprietary format to get locked into and no black box between your systems and the rail.
Service writers, fleet ops, and platform owners see only what their role allows. Enforced at the engine, not the UI.
Every stage change, cap, and transfer is recorded. Reconciliation is provable, not reconstructed.
Money moves on rails the providers already trust, with KYC, idempotency, and dispute handling built in.
BayLink is settlement and coordination infrastructure for autonomous vehicle fleet servicing. It connects AV fleet operators to independent service providers (tire, body, LIDAR calibration, charging) and settles every work order automatically, capped up front and released the moment the vehicle returns.
Each job is an envelope with a price cap set in advance. When the vehicle returns, the actual amount is released against the cap, never over, and transferred to the service provider through Stripe Connect.
ACP is an open specification, published under Apache 2.0, for expressing automotive service work orders, pricing, and settlement intent as structured envelopes. It includes a public conformance suite so any implementation can validate without proprietary dependencies.
Two sides of one rail: AV fleet operators who need to keep vehicles in service without owning a service network, and independent service providers who want fleet work and immediate payment on completion.
Vertically integrated operations cover dense routes and obvious services but cannot economically reach the long tail of independent providers. BayLink is network-neutral rails: it does not compete with operators or shops, it connects them, onboarding a provider in a day rather than a quarter.
Access is role-scoped and enforced at the engine, every stage change, cap and transfer is written to an append-only audit record, and money moves on Stripe Connect with KYC, idempotency and dispute handling built in.
We're onboarding pilot operators and providers now. If you run a fleet, or a shop that services one, let's talk.