Altitude Cleaning Crew logo
Developer and agent resources

Altitude Cleaning Crew Developer & Agent Resources

ACC exposes one narrow public integration: customer-authorized cleaning quote and contact requests. It is not a general scheduling, customer-record, cleaner, or payments API.

Safe quickstart

Start by reading the OpenAPI description. Do not submit a test lead. Use the POST endpoint only when a real customer has explicitly asked Altitude Cleaning Crew to contact them.

curl -H "Accept: application/json" \
  https://www.altitudecleaningcrew.com/api/v1

No API key is required. Do not send an Authorization header. Customer contact details and explicit communications consent are required for lead submission.

Official resources

API discovery and status

Safe JSON API root with version, status, documentation, and supported links.

/api/v1

OpenAPI 3.1 specification

Machine-readable contract for the versioned Lead Intake API.

/openapi.json

API documentation

Request fields, response behavior, limits, and lifecycle policy.

/api-docs

Authentication guide

Anonymous access rules and customer-authorization requirements.

/auth.md

RFC 9727 API catalog

Predictable machine discovery for the supported API surface.

/.well-known/api-catalog

Agent instructions

When to use Altitude Cleaning Crew and how to route customer requests.

/llms.txt

Versioning and deprecation

The supported endpoint is /api/v1/leads. Breaking changes require a new URL version such as /api/v2/leads.

The legacy /api/leads alias remains available for existing ACC forms and returns a standards-based Deprecation header plus links to this policy and its successor.

ACC will provide at least 365 days of notice before removing a public API version. A scheduled removal will be announced with Deprecation and Sunset response headers and documented here. No sunset date is currently scheduled.

Rate limits

Lead and application submissions are limited to 10 requests per minute per client at the serving edge. Responses include RateLimit-Limit, RateLimit-Remaining, RateLimit-Reset, and RateLimit-Policy.

A 429 response includes Retry-After and an RFC 9457 application/problem+json body. Additional abuse controls may reject automated or unsolicited traffic sooner.

Current product boundaries

  • No public sandbox.
  • No official CLI, SDK, MCP server, or webhook product.
  • No API access to customer, cleaner, schedule, payment, or Fieldd records.
  • No test, duplicate, unsolicited, or fabricated leads.

Integration questions: contact Altitude Cleaning Crew.