Vasquez Auto Glass Developer Portal

Read-only public business and service data for Vasquez Auto Glass, an auto glass shop in Houston, Texas. Built for AI agents and for developers who need the shop’s services, hours and contact details in a machine-readable form.

Quickstart

No signup, no key, no client library. Three calls cover the whole API.

# What does this business do, where, and how do you reach it?
curl -s https://vasquezautoglass.com/api/v1/site

# Which services does it offer?
curl -s https://vasquezautoglass.com/api/v1/services

# One service in detail
curl -s https://vasquezautoglass.com/api/v1/services/windshield-replacement

Authentication

None, by design. Every endpoint is public and read-only. There are no API keys to issue, no OAuth flow and no rate-limit tiers, because there is nothing here to protect or meter — the data is the same information printed on the public pages of this site.

Please keep request volume reasonable. This is a small business on shared hosting, not a platform. Cache what you fetch; the data changes rarely.

Sandbox

There is no separate sandbox, and none is needed. The API accepts only GET, HEAD and OPTIONS; it creates no quotes, appointments, contracts, payments or customer records. Any write method answers 405. Calling production is therefore side-effect free — treat it as the sandbox.

Endpoints

• GET /api/v1 — discovery index
• GET /api/v1/site — name, address, phone, hours, service area, vehicle and glass types
• GET /api/v1/services — service catalog
• GET /api/v1/services/{slug} — one service

The same data is also served over the standard WordPress REST namespace at /wp-json/vag-agent/v1/.

Specification

• OpenAPI 3.1 specification — /openapi.json
• llms.txt — site map for language models, with when-to-use guidance
• llms-full.txt — extended context, vehicles, glass types, boundaries
• agent-instructions.md — when to use this business and what not to claim on its behalf
• XML sitemap

Content negotiation

Pages answer Accept: text/markdown with text/markdown; charset=utf-8 and send Vary: Accept, Accept-Encoding, per acceptmarkdown.com. Every page also has a markdown sibling, which is the cheapest way to fetch one:

curl -s -H 'Accept: text/markdown' https://vasquezautoglass.com/
curl -s https://vasquezautoglass.com/index.md
curl -s https://vasquezautoglass.com/contact-us/index.md

Errors

Errors use RFC 9457 Problem Details with application/problem+json, plus stable code and resolution fields so a client can branch on the failure without parsing prose.

curl -s https://vasquezautoglass.com/api/v1/does-not-exist

{
  "type": "about:blank",
  "title": "API route not found",
  "status": 404,
  "detail": "The requested API route does not exist.",
  "code": "api_route_not_found",
  "resolution": "Read /openapi.json or GET /api/v1 for the supported read-only routes."
}

A missing page returns a real 404. Ask for markdown and the body is a short recovery list pointing at the sitemap, llms.txt and this page.

Contact

Vasquez Auto Glass · 722 Broadway St, Houston, TX 77012 · (713) 921-9280 · contact form