---
title: JOY Automart Agent Integration Guide
description: Public configuration, usage, authentication, and safety guidance for automated clients interacting with JOY Automart.
last_updated: 2026-08-11
canonical: https://www.joyautomart.com/AGENTS.md
---

# JOY Automart Agent Integration Guide

> This guide defines the public, read-only discovery boundary for automated clients. It does not grant access to Owner/Admin controls, private agents, customer data, internal tools, or write operations.

## Installation

No client package is required to read JOY Automart's public resources. Use an HTTPS client that follows standard HTTP status codes and content types.

```bash
curl --fail --silent --show-error https://www.joyautomart.com/llms.txt
curl --fail --silent --show-error https://www.joyautomart.com/openapi.json
curl --fail --silent --show-error -H 'Accept: text/markdown' https://www.joyautomart.com/
```

For repository-local development of JOY's standalone stdio MCP adapter, follow the separate repository MCP documentation. The existence of that adapter does not mean a public remote MCP endpoint is available on `www.joyautomart.com`.

## Configuration

Use `https://www.joyautomart.com` as the public website origin. Public discovery resources include:

- `/llms.txt`
- `/llms-full.txt`
- `/index.md`
- `/sitemap.md`
- `/glossary.md`
- `/openapi.json`
- `/sitemap.xml`

Send `Accept: text/markdown` when a Markdown representation of a public SPA page is preferred. Clients should honor `Content-Type`, `Link`, `Cache-Control`, `Vary`, authentication requirements, and HTTP status codes.

## Usage

A safe public discovery flow is:

1. Read `/llms.txt` for the supported public resource index.
2. Read `/index.md` or request the homepage with `Accept: text/markdown` for structured context.
3. Read `/sitemap.md` to locate public product areas.
4. Read `/openapi.json` before making any documented public API call.
5. Treat a `404` from an unadvertised protocol-discovery URL as “not supported.” Do not infer MCP, A2A, UCP, ACP, Web Bot Auth, or another protocol simply because JOY uses agents internally.

Example public API call:

```bash
curl --fail --silent --show-error https://www.joyautomart.com/api/health
```

## Authentication and authorization

Public documentation does not grant mutation authority. Owner/Admin pages, deployments, private HERMES functions, account records, customer or staff information, finance, integrations, production controls, and other privileged operations require the relevant authenticated JOY session and governance decision.

Do not attempt to bypass authentication, CSRF protection, capability restrictions, kill switches, certification gates, rate limits, or audit controls. A public URL that is not documented in `/openapi.json` should not be assumed to be a public API contract.

## Safety

- Do not represent a proposed action as executed unless JOY returns execution evidence for that action.
- Do not invent vehicle compatibility, OEM part numbers, prices, stock, repair procedures, or production status.
- Treat VIN, chassis, engine, model year, drivetrain, market specification, and supersession as relevant fitment inputs where applicable.
- Treat DTC codes and symptoms as diagnostic evidence, not a complete diagnosis.
- Use the minimum required capability and preserve server-side authorization boundaries.
- Respect privacy, rate limits, robots directives, and authenticated/private route exclusions.

## Error handling

Use HTTP semantics directly: `2xx` indicates the requested representation or operation succeeded; `4xx` indicates the client request is unsupported, unauthorized, invalid, or not found; `5xx` indicates temporary server-side unavailability. Do not reinterpret a SPA HTML document as a machine protocol response.

## Sitemap

See the [public sitemap](https://www.joyautomart.com/sitemap.md) and [automotive glossary](https://www.joyautomart.com/glossary.md) for additional navigation and terminology.