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 company’s services, service areas 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.

Rate limits

Every API response carries the standard IETF rate-limit headers, so a client can self-throttle without guessing:

RateLimit-Limit: 120
RateLimit-Remaining: 119
RateLimit-Reset: 47
RateLimit-Policy: 120;w=60

The quota is 120 requests per 60 seconds per client address. Going over returns 429 with Retry-After and a problem body whose code is rate_limited. The counter is real, not advisory.

Versioning and deprecation

The API is versioned in the URL path. The current version is 1.0.0 and its status is stable.

Breaking changes ship as a new version under a new path, never in place. A retiring version is announced with Deprecation and Sunset headers (RFC 8594) at least 180 days before it stops answering, and the successor is linked from the same response.

Every response carries an API-Version header. While a version is being retired its responses also carry Deprecation and Sunset (RFC 8594) plus a Link to the successor, so a client can detect the change from the response alone rather than by reading this page:

API-Version: 1.0.0
Deprecation: Tue, 01 Sep 2026 00:00:00 GMT
Sunset: Sun, 01 Mar 2027 00:00:00 GMT
Link: <https://vasquezautoglass.com/api/v2>; rel="successor-version"

Nothing is scheduled for retirement today, so no Deprecation or Sunset header is sent. The same policy is machine-readable under versioning in the discovery index.

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, service areas, differentiators, estimated price ranges
GET /api/v1/services — service catalog
GET /api/v1/areas — city hubs served
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 — brand context, ideal customer profiles and crawling notes for AI assistants
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

Example responses

What each endpoint actually returns, so a client can be written against real shapes rather than guessed ones.

GET https://vasquezautoglass.com/api/v1/site

{
  "name": "Vasquez Auto Glass",
  "phone": "(713) 921-9280",
  "mobile_service": true,
  "service_areas": ["Houston, TX", "Greater Houston area"],
  "pricing_note": "No price is published. Every job is quoted per vehicle...",
  "quote_policy": "..."
}

GET https://vasquezautoglass.com/api/v1/services

[
  {
    "slug": "windshield-replacement",
    "name": "Windshield Replacement",
    "url": "https://vasquezautoglass.com/windshield-replacement/",
    "description": "Full front windshield replacement for cars, SUVs, vans..."
  }
]

Status codes

Status	code	When
`200`	`—`	The resource was found and returned.
`404`	`service_not_found`	The {slug} does not match any published service. Call listServices for valid slugs.
`404`	`api_route_not_found`	The path is not one of the documented routes. Read /openapi.json.
`404`	`page_not_found`	A site URL that does not exist, requested as JSON.
`405`	`method_not_allowed`	Anything other than GET, HEAD or OPTIONS. The API is read-only.
`406`	`—`	The Accept header asks for a representation this site does not produce.
`429`	`rate_limited`	Over the quota. Read Retry-After and the RateLimit-* headers.

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