Diagnose the vehicle. Verify the part. Move with evidence.

Automotive intelligence from problem to next action

JOY Automart connects vehicle diagnostics, fitment-aware automotive parts sourcing, workshop and dealer workflows, retail vehicle commerce, logistics, and JOY VELLOX bespoke engineering. The platform is built for drivers, workshops, dealers, trade partners, suppliers, and automotive teams that need a clearer route from a vehicle problem or commercial requirement to the right next step.

Vehicle identity matters. VIN or chassis context, model year, engine, drivetrain, market specification, option information, OEM references, and part supersessions can all affect compatibility. JOY therefore treats generic product matching as discovery rather than guaranteed fitment and keeps “verification required” as a valid answer when exact evidence is unavailable.

Diagnostics, parts and operating systems

Diagnostic Trouble Codes and symptoms are evidence inputs, not automatic root-cause diagnoses. A complete repair decision may require scan data, live measurements, service history, physical inspection, wiring and power checks, technical procedures, and post-repair verification. JOY’s public information helps organize that path without presenting an unverified hypothesis as a completed repair.

Trade OS supports B2B sourcing and trade workflows. Dealer OS supports dealer and vehicle-commerce operations. Workshop OS supports service, diagnostic, parts, job, and evidence-oriented workshop workflows. Public pages describe these capabilities; account-specific records, prices, credit, orders, write operations, and private business data remain behind authenticated JOY systems.

JOY VELLOX bespoke engineering

JOY VELLOX is JOY Automart’s bespoke engineering and personalization line for concept-led vehicle transformation, wheels, exterior work, interiors, and related engineering. Public concepts establish design direction, not a guaranteed final specification. Vehicle compatibility, safety, regulatory suitability, pricing, and delivery timing are confirmed through the relevant VELLOX project process.

AI that preserves authority boundaries

HERMES is JOY Automart’s agent framework and MAYA is the public AI receptionist and automotive assistant. Public AI access does not expose Owner/Admin privileges. A model recommendation is not proof that an external action occurred. Privileged operations, deployments, customer or staff records, financial functions, integrations, and production controls require the appropriate authenticated session, authorization, validation, and execution evidence.

For automated clients, JOY publishes explicit machine-readable resources and returns HTTP 404 for unsupported protocol-discovery endpoints rather than returning a misleading SPA document. Clients should use the public OpenAPI contract only for documented interfaces and should not infer MCP, A2A, UCP, ACP, Web Bot Auth, or other protocol support from JOY’s internal architecture.