Help your customer reach the shop.

Public information

Read business facts and capabilities, confirmed services, and the OpenAPI specification. Only listed services are confirmed. Ask about vehicle-specific coverage.

Submit an inquiry

Use the inquiry form or POST JSON to /api/v1/inquiries. No API key or registration is required. Supply an Idempotency-Key header of 16–100 letters, numbers, underscores, or hyphens. Keep it unchanged when retrying the same request.

Get the customer’s permission before sharing their information. Required fields are name, preferredContact (email or phone), message, and consent: true. Supply the selected contact detail. Vehicle year, make, and model are optional. A different payload needs a new key.

What success means

A 201 response (or 200 for a retry) means the inquiry is stored, with a reference and status of received. Tell the customer that the shop will follow up: no appointment, service date, price, or repair authorization has been created. There is no public inquiry lookup.

Failures and limits

Correct 422 field errors before retrying. A 409 means the key was used for different details. Respect Retry-After on 429 limits. Retry temporary 503 failures with the same key. Default limits are 30 attempts per minute per IP and five accepted inquiries per rolling hour per normalized contact. There is no special exemption for AI agents.

Browser tools

Supported browsers expose business information and inquiry submission through WebMCP on the request page. The form and HTTP API work independently of WebMCP. A challenge or required permission must be handled by the customer. Never bypass it.