Docs
Documentation for the product boundary that exists today.
Operator reference
The current notes cover account access, VIN context, wallet funding, and records. They do not represent a live keycode-provider integration.
- 01
Quick Start
Start with reviewed account access, VIN context, and wallet-funding boundaries before planning higher-level operator work.
- 02
Auth & Access
Keep platform access scoped to approved business users, and separate server-side secrets from browser-facing tokens.
- 03
API Surface
FCA keycode execution is live for supported vehicles; additional manufacturers are being added.
- 04
Operational Safety
Keep account, VIN, funding, records, and provider authority separate so one completed step never implies another.
Reference
Core integration areas
- Reviewed account access and VIN context
- Stripe-hosted wallet funding and transaction records
- Provider execution gated pending production verification
Implementation notes
Keep public and customer-facing states calm and explicit: show the vehicle context first, keep wallet funding separate, and do not present provider execution until its full contract is verified.