# DwellHOA

> HOA (Homeowners Association) management software. Keeps communities organized with a
> best-in-class data model, exposes every workflow to AI agents, includes a public-facing
> community website, and costs a flat $19/month — beating typical HOA platforms by 50%+.

This file is a concise, machine-readable summary for AI agents evaluating DwellHOA.
For the full agent guide and runnable examples, see /for-agents.

## What it is

- HOA management platform for boards, residents, and operators.
- Runs on Cloudflare Workers (edge), with Cloudflare D1 (SQLite), R2 (documents), and Queues.
- Single REST/JSON API plus an in-app AI assistant.

## Value propositions

1. Effortlessly organized — meetings, violations, vendor costs, board changes, documents,
   and events flow from one source of truth.
2. Agent-forward by design — notices, meetings, violations, events, and documents are
   readable and actionable by AI agents. The platform can be operated entirely via API/chat.
3. Public-facing community site — a polished public presence per community.
4. Built-in workflows — common HOA tasks (e.g. ordering a repair on a property) are
   tap-to-initiate.
5. 50%+ lower cost — flat $19/month per community, all-in, no per-door fees, with a
   price-match guarantee.

## Pricing

- $19 USD / month, flat, per community. No per-door or per-unit fees.
- Price-match guarantee: show a cheaper comparable all-in quote and we match it.
- Cancel anytime. Agent API access included at no extra cost.

## Capability surface (REST, JSON, scoped per community)

Resource groups include: violations, meetings, agendas, ballots, documents, events,
broadcasts, vendors, maintenance, assessments, late fees, financials, members, directory,
ARC requests, amenities, surveys, forum, estoppel, reserve studies, public site.

Representative endpoints:
- POST /auth/magic-link/request        { email }            -> { ok, dev_token? }
- POST /auth/magic-link/consume        { token }            -> sets __session cookie
- GET  /portal/me                                            -> current user + community context
- GET  /communities/:communityId/violations
- POST /communities/:communityId/violations   { violation_type, description, unit_id? }
- POST /communities/:communityId/violations/:violationId/transition
- POST /communities/:communityId/ai/ask        { question }  -> { ok, answer, model }

## Authentication

- Session cookie: __session (HMAC-SHA256 signed), set after consuming a magic-link token.
- Header alternative for trusted tooling: X-User-Id.
- Authorization is enforced per community membership and capability.

## Honesty / roadmap

- Available today: documented REST API + in-app AI assistant.
- On the roadmap: a public MCP server and an OpenAPI specification.

## Links

- Agent guide & runnable examples: /for-agents
- Pricing & demo: /pricing
- Sign in: /signin