Maid in Allen TX Developer Portal

Read-only public business and service data for Maid in Allen TX, a residential cleaning company in Allen, 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://maidinallentx.com/api/v1/site

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

# One service in detail
curl -s https://maidinallentx.com/api/v1/services/bi-weekly-cleaning

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.

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/mia-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://maidinallentx.com/
curl -s https://maidinallentx.com/index.md
curl -s https://maidinallentx.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://maidinallentx.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

Maid in Allen TX · 1420 W. McDermott, Allen, TX 75013 · (214) 317-1867 · contact form