# JOY Automart — Full Agent Context > JOY Automart is an automotive intelligence company connecting vehicle diagnostics, fitment-aware parts sourcing, workshop and dealer operating systems, retail automotive commerce, logistics, and JOY VELLOX bespoke engineering. ## Platform purpose JOY Automart helps drivers, workshops, dealers, trade partners, suppliers, and automotive teams move from a vehicle problem or commercial need to an evidence-backed next action. Public surfaces support discovery and information. Authenticated operating surfaces add business context and controlled workflows. Privileged actions remain behind JOY Governance and must not be inferred from public content. ## Automotive Intelligence JOY automotive intelligence is designed around vehicle identity, fault context, compatible-part reasoning, sourcing, workshop operations, and outcome evidence. VIN and vehicle attributes can be used to narrow fitment. Diagnostic information should distinguish hypotheses from verified faults and should not invent OEM part numbers, repair procedures, prices, or completed actions. ## HERMES and MAYA HERMES is JOY Automart’s agent framework. MAYA is the public AI receptionist and automotive assistant. Public AI access does not expose Owner/Admin authority. Responses from an AI surface are advisory unless the product explicitly returns execution evidence for an authorized action. ## Trade OS Trade OS supports automotive B2B discovery and sourcing workflows. It is intended to help workshops and trade buyers identify needs, compare relevant inventory or sourcing options, and coordinate procurement. Commercial terms, stock, pricing, credit, settlement, and write operations are authoritative only when returned from authenticated JOY systems. ## Dealer OS Dealer OS supports dealer and vehicle-commerce workflows. Public descriptions are informational. Dealer records, customer data, commercial offers, inventory mutations, financial actions, and operational decisions require authenticated authorization. ## Workshop OS Workshop OS supports workshop operations, vehicle service context, diagnostics, parts, job workflows, and commissioning-oriented evidence. Diagnostic output must not be treated as a substitute for qualified inspection or OEM procedure authority where safety-critical work is involved. ## JOY VELLOX JOY VELLOX is JOY Automart’s bespoke vehicle engineering and personalization line. Public pages may present concepts, design directions, wheels, exterior work, interiors, and engineering themes. Final specification, compatibility, safety, pricing, timing, and regulatory suitability are confirmed through the appropriate project process. ## Parts and fitment Fitment depends on the exact vehicle configuration. VIN, chassis, model year, engine, drivetrain, market specification, supersession, and OEM references can matter. Automated clients should never infer guaranteed compatibility from a generic product title alone. Where exact fitment is unavailable, the correct state is “verification required.” ## Diagnostics DTC codes and symptoms are evidence inputs, not complete diagnoses. A safe diagnostic path considers scan data, freeze-frame information, live data, service history, physical inspection, wiring, power supply, known technical information, and post-repair verification as applicable. ## Public API The public OpenAPI document at https://www.joyautomart.com/openapi.json documents only interfaces JOY intentionally exposes for unauthenticated machine discovery. The public health endpoint is read-only. The existence of internal APIs, authenticated APIs, MCP adapters, agents, or Owner/Admin controls does not make them public. ## Agent and protocol policy JOY publishes only protocol discovery documents that correspond to a real supported public protocol surface. Three are published and served: - https://www.joyautomart.com/.well-known/agent-card.json — A2A 1.0 agent card for the authenticated, read-only JOY A2A JSON-RPC gateway at https://www.joyautomart.com/a2a. - https://www.joyautomart.com/.well-known/api-catalog — RFC 9727 linkset naming the public OpenAPI document and the agent integration guide. - https://www.joyautomart.com/.well-known/agent-permissions.json — declared permissions, rate expectations and prohibited actions for automated clients. Unsupported MCP, UCP, ACP, x402, NLWeb, Web Bot Auth, agents.json, or other discovery endpoints intentionally return HTTP 404, and a missing file under /.well-known/ returns 404 rather than an HTML document. Clients must not infer support from the general capabilities of the JOY application or repository. ## Markdown mirrors Every public page has a Markdown mirror at the same path with a .md suffix; the homepage mirror is https://www.joyautomart.com/index.md. Mirrors are discoverable three ways: by appending .md to the path, by following the Link rel="alternate" type="text/markdown" response header, or by sending Accept: text/markdown. Mirrors are served as text/markdown; charset=utf-8 and link back to their HTML page with Link rel="canonical". ## Authentication and authority Owner/Admin routes, deployments, private agent controls, customer or staff records, write operations, privileged integrations, financial functions, and production authority require authentication and JOY Governance. Public documentation grants no mutation permission. An automated client should request the minimum capability needed and must respect server authorization, rate limits, validation, and audit boundaries. ## Reliability and evidence JOY distinguishes configured capability from verified execution. A control may be visible while its runtime is unavailable. A model may respond while an external action is not authorized. Production evidence should include the relevant runtime or execution identifier when a surface claims an action occurred. Failures should remain visible rather than being represented as successful. ## Public navigation - https://www.joyautomart.com/ - https://www.joyautomart.com/intelligence - https://www.joyautomart.com/trade-os - https://www.joyautomart.com/dealer-os - https://www.joyautomart.com/joy-vellox - https://www.joyautomart.com/catalog - https://www.joyautomart.com/workshops - https://www.joyautomart.com/technology - https://www.joyautomart.com/experience-centre - https://www.joyautomart.com/enterprise - https://www.joyautomart.com/suppliers - https://www.joyautomart.com/logistics - https://www.joyautomart.com/credit - https://www.joyautomart.com/insights - https://www.joyautomart.com/journal - https://www.joyautomart.com/thesis - https://www.joyautomart.com/about - https://www.joyautomart.com/press - https://www.joyautomart.com/careers ## Machine-readable resources - https://www.joyautomart.com/llms.txt - https://www.joyautomart.com/llms-full.txt - https://www.joyautomart.com/index.md - https://www.joyautomart.com/sitemap.md - https://www.joyautomart.com/sitemap.xml - https://www.joyautomart.com/glossary.md - https://www.joyautomart.com/AGENTS.md - https://www.joyautomart.com/openapi.json - https://www.joyautomart.com/.well-known/api-catalog - https://www.joyautomart.com/.well-known/agent-permissions.json - https://www.joyautomart.com/.well-known/agent-card.json ## Sitemap See the full [agent-readable sitemap](https://www.joyautomart.com/sitemap.md) for public routes and resource grouping.