How Abode runs
property operations.
This is the operator's reference for the model behind Abode — portfolio structure, maintenance execution, leasing, communication, payment rails, accounting controls, and repeatable reporting. Start anywhere; every page links back to the model.
Core operating domains
Implementation-facing docs
Covering rails to reports
Ship your first automation
- 01Create workspace
Name your portfolio, invite your team.
- 02Connect rails
Stripe + Plaid in under 2 minutes.
- 03Import records
CSV upload or ask Abode to scrape.
- 04Turn on autopilot
Pick what Abode runs unattended.
The operating model
Orient the team around Abode's operating model.
Jump into the agent layer — world model, actions, proactive events, and the reasoning surface.
Model rentals and associations so every record is correct.
Portfolio records, units & occupancy, and mixed rental / HOA portfolios.
Move a request from intake through vendor execution.
AI intake, work-order lifecycle, and the vendor portal.
Run leasing from applicant data through signed renewal.
Pipeline, AI-parsed fields, and the e-signature handoff.
Keep tenant, owner, vendor, and team outreach tied to the record.
Record-anchored messaging, audience routing, and portal-specific surfaces.
Collect, reconcile, and enforce trust rules with confidence.
Rails, stablecoin architecture, reconciliation, and three-way trust.
Repeatable dashboards for month-close, owner packets, and audits.
Recurring report packets and the owner-portal statement surface.
Interactive examples
Late-rent flow
How Abode moves a late payment from detection to resolutionDetection
Abode watches the ledger and reconciliation feed. A payment is flagged late once grace window + 24h elapse with no matched deposit.
- Grace window read from lease
- Partial payments tracked separately
- ACH in-flight is not "late"
{
"event": "rent.late_detected",
"tenant_id": "tnt_4B_maple",
"amount_due": 1850.00,
"days_late": 3,
"grace_window": 2,
"auto_actions": ["draft_reminder"]
}Role access matrix
Who sees what. Click a role to filter.| Capability | Admin | Manager | Owner | Tenant | Vendor |
|---|---|---|---|---|---|
| View portfolio dashboard | ✓ | ✓ | |||
| Edit property + unit records | ✓ | ✓ | |||
| Record a payment | ✓ | ✓ | |||
| Approve vendor invoice | ✓ | ✓ | |||
| Submit a maintenance request | ✓ | ✓ | ✓ | ✓ | |
| Pay rent / view payment history | ✓ | ||||
| Submit a quote or invoice | ✓ | ||||
| Export accounting reports | ✓ | ✓ |
Data model at a glance
Hover an entity to trace its relationships.Hover a node — relationships highlight.
API playground
Sandbox · no writes, no auth
{
"data": [
{
"id": "packet_01J8V1VCX2A7D9V0DFW5M7Q3RQ",
"name": "April owner packet",
"cadence": "MONTHLY",
"scheduleTimeZone": "America/Chicago",
"scheduleTimeOfDay": "09:00",
"recipients": ["owners@theabode.ai"],
"latestDeliveryStatus": "READY",
"isPaused": false,
"items": [
{ "savedViewId": "sv_rent_roll", "position": 0 },
{ "savedViewId": "sv_owner_statement", "position": 1 },
{ "savedViewId": "sv_unpaid_bills", "position": 2 }
]
}
]
}Abode AI
The agent layer that turns Abode from a system of record into a system of intelligence. Every domain — leasing, maintenance, accounting, comms — is exposed to the agent as typed actions, gated by approvals.
World model
Four parallel fetchers hydrate a per-org snapshot — properties, ledgers, work orders, conversations — into a deterministic cache. Every prompt sees fresh, scoped context without a round-trip storm.
Actions surface
150+ typed actions across 11 domains: properties, leases, tenants, work orders, vendors, payments, accounting, communications, owners, reports, settings. Each action is permission-gated and produces a deterministic audit row.
Proactive events
40+ event triggers (rent overdue, COI lapsed, vacancy threshold, vendor SLA breach) fire bound action chains. The agent proposes; you approve. Nothing autonomous touches money without a human signoff.
Reasoning & Feedback
Ten tunable reasoning chains (late-rent triage, lease-renewal pricing, work-order routing, and more) with 30+ few-shot examples. Implicit signals—approve, edit, dismiss, escalate—feed a per-org tuning log, so the agent sharpens for your portfolio automatically.
Customization
Your agent adapts to how you run your properties — set its tone, triggers, and guardrails to match your style. Every rule is yours to define, so Abode's AI works the way you would, not from a generic template.
Communication (Beta)
Reach your agent however you work—through the Abode web app, mobile app, or iMessage, with more channels coming soon. Your agent meets you where you already are, no new habits required.
Surface lives in the management dashboard and role-scoped portals, not in a public REST API today. The endpoints below under API reference are the ones currently exposed.
How Abode assembles a live, scoped snapshot of your portfolio for every prompt.
Properties
Model rentals and associations so every record — address, unit, owner, docs — is correct and linked. Property CRUD runs in the management dashboard today; HOA-scoped workflows (violations, architectural requests) are the first property-adjacent endpoints exposed over the API.
Portfolio records
Every property carries its owner entity, units, and bank splits. The dashboard is the authoritative write surface; API surfaces are being added as each workflow stabilizes.
Units & occupancy
Each unit tracks leased / vacant / under-renovation state, turnover history, and amenities. Occupancy rolls straight into reports.
Mixed portfolios
Rentals and associations live in the same workspace but keep distinct workflows — associations carry violations and architectural approvals that rentals don't.
Tenants
One record per tenancy — with contact preferences, balance, and a full communication history attached. Tenant reads and writes run through the management dashboard and portals; there is no stable public REST surface for tenants today.
Identity & contacts
Name, emails, phones, preferred channel (SMS / email / portal). Abode routes reminders through the right one automatically.
Balance & payments
Open balance, scheduled charges, and a payment timeline per tenancy. Partials split to the oldest open charge first.
Conversation history
Every tenant message — in any channel — is pinned to the tenancy record so the next person picking it up has context.
Surface lives in the management dashboard and role-scoped portals, not in a public REST API today. The endpoints below under API reference are the ones currently exposed.
Leases
Applicant → draft → signed → active → renewed. Two workflows are exposed over the API today: AI-assisted lease parsing and the e-signature handoff.
Pipeline
Listings, applicants, draft leases, and renewals surface in a single pipeline. Management stays in the dashboard for most edits.
Parsed fields
POST /api/dashboard/leasing/parse turns raw lease text or uploaded files into structured fields (tenant, rent, deposit, dates, lease type, notable terms). Intended to accelerate review, not to skip legal validation.
E-signature
POST /api/dashboard/leasing/e-signature sends a document for signature. PATCH with status=SIGNED activates the lease. Contract is provider-shaped so a DocuSign / Dropbox Sign integration can slot in later.
- POST/api/dashboard/leasing/parse
- POST/api/dashboard/leasing/e-signature
- PATCH/api/dashboard/leasing/e-signature
Maintenance
Intake → triage → dispatch → close. Work-order lifecycle runs as an explicit state machine; AI parsing and the vendor portal are the routes exposed today.
AI intake
POST /api/dashboard/maintenance/parse extracts title, description, priority, category, property address, unit, and reporter from raw text or images. Designed for assisted data entry, not unsupervised autonomous creation.
Lifecycle
OPEN → QUOTED → APPROVED → SCHEDULED → IN_PROGRESS → RESOLVED → CLOSED. The API enforces allowed transitions; operators and vendors move the ticket through.
Vendor portal
GET /api/vendor-portal/work-orders lists a vendor's assigned work with pagination, status filters, cost, schedule, notes, and property / unit context.
- POST/api/dashboard/maintenance/parse
- GET/api/vendor-portal/work-orders
Vendors
Vendor execution lives on the work order. The vendor portal is intentionally narrow — execution surface, not a secondary management dashboard. Scorecards, compliance tracking, and vendor payouts are dashboard workflows today.
Portal contract
Vendors see quotes, schedule updates, notes, and payment status for the work orders assigned to them. Response from /api/vendor-portal/work-orders includes estimated and actual cost, message counts, and a scoped tenancy block.
Billing handoff
A resolved work order with actual cost and vendor context can generate a bill. Paying that bill posts a balanced journal entry and, when owner funds are involved, a trust-ledger movement — no duplicate data entry.
Compliance
COI and W-9 expiry are tracked per vendor. Scoring, payouts, and compliance enforcement run in the dashboard today; a public vendor-management API is not shipped.
Payments
Collect, reconcile, and enforce trust-account rules. ACH, cards, cash, and stablecoins — all on the same ledger.
Rails
ACH (T+1), debit (instant), wire, cash, and stablecoins (near-instant). Abode picks the cheapest rail that meets your deadline.
Stablecoins & Circle Wallets
Tenants can pay in USDC from any non-custodial wallet — MetaMask, Coinbase Wallet, Phantom, hardware wallets. Funds land in a user-scoped Circle Wallet and auto-convert to USD on deposit, or stay onchain for cross-border owners. Fully non-custodial infrastructure, 1:1 redemption.
Abode Earn (Coming Soon)
Idle balances earn yield — best-in class APY, same-day liquidity. Interest allocates to the designated ledger (owner vs. property) with a full audit trail.
Reconciliation
Bank feed, onchain feed, and ledger auto-match. Unmatched items land in a dedicated queue — no spreadsheet.
Trust controls
Holdbacks, reserves, and owner-disbursement rules encoded per property. Stablecoin payouts respect the same rules. Exports are auditor-ready.
- POST/api/payments/create-intent
- POST/api/dashboard/accounting/bank-reconciliation/[id]
Communication
Tenant, owner, vendor, and team outreach — all tied to the underlying record. Announcements, threads, and portal messaging run inside the dashboard today; there is no stable public REST surface for communications.
Anchoring
If the message is about a job, it belongs on the work order. If it's about a balance or lease, it stays with the tenancy. Broad, non-record-specific outreach goes through announcements. The operational value is preserving the next action, not just message delivery.
Audience routing
Tenants, owners, vendors, and internal staff do not share one feed. Tone, evidence requirements, and visibility rules differ by audience — that is reflected in separate surfaces rather than one unified inbox.
Record-first
Every tenant-portal, vendor-portal, or owner-portal message is pinned to the operational object, so handoffs do not lose context. Detached outreach is the failure mode to avoid.
Surface lives in the management dashboard and role-scoped portals, not in a public REST API today. The endpoints below under API reference are the ones currently exposed.
Reports
Repeatable delivery beats one-off exports. Report packets turn saved views into recurring workflows; the owner portal exposes the same data with a narrower, read-only scope.
Report packets
GET/POST/DELETE /api/dashboard/reports/packets manages recurring packets of saved views with cadence, recipients, time zone, and pause state. The dispatch layer treats delivery as operational, not cron trivia.
Owner portal statements
GET /api/owner-portal/statements aggregates completed payments, transactions, and management fees into property-level statements plus portfolio totals — scoped to the owner's assigned properties.
Report catalog
Financial (income statement, balance sheet, cash flow, GL, trial balance), leasing/occupancy (rent roll, delinquent tenants, leases ending, vacant units), operations (work orders, open tasks, unpaid bills), and owner-facing statements all run through the same report runtime.
- GET/api/dashboard/reports/packets
- POST/api/dashboard/reports/packets
- DELETE/api/dashboard/reports/packets
- GET/api/owner-portal/statements
Implementation guides
Month-end close in 30 minutes
The repeatable checklist for reconciling rent, fees, and trust balances each month.
Accounting · 12 min read
Roll out Autopilot to your team
Which rules to turn on first and how to review Abode's decisions without slowing down.
Operations · 8 min read
Chart of accounts mapping
Map your existing COA to Abode so reports stack up against your legacy books.
Accounting · 15 min read
Train Abode on your voice
Upload your past tenant emails — Abode learns tone, cadence, and boundaries.
Communication · 6 min read
Trust account controls
Setting holdbacks, reconciliation windows, and auditor-friendly exports.
Financial · 10 min read
Vendor quote comparison
How to turn three quotes into one decision without leaving the ticket.
Maintenance · 7 min read
API reference
Leasing
3 endpoints
/api/dashboard/leasing/parseAI-extract structured lease fields (tenant, rent, deposit, dates, terms) from text or uploaded documents./api/dashboard/leasing/e-signatureSend a lease for e-signature; persists a signature transaction and routes to the tenant./api/dashboard/leasing/e-signatureApply a signature status update (e.g. SIGNED) — moves the lease toward ACTIVE when complete.Maintenance
2 endpoints
/api/dashboard/maintenance/parseAI-parse a resident request into a work-order candidate (title, priority, category, property, unit, reporter)./api/vendor-portal/work-ordersVendor portal: list assigned work orders with pagination, status filters, and property/unit context.Payments
2 endpoints
/api/payments/create-intentCreate a Stripe PaymentIntent — card or ACH via us_bank_account. Live today./api/dashboard/accounting/bank-reconciliation/[id]Apply reconciliation actions: import lines, auto-match, manual items, complete, or void.Reports
4 endpoints
/api/dashboard/reports/packetsList recurring report packets configured for the workspace./api/dashboard/reports/packetsCreate a packet from saved views, with cadence and recipient list./api/dashboard/reports/packetsArchive a packet (id passed as query parameter)./api/owner-portal/statementsOwner portal: property-scoped statements with portfolio totals for a period.Associations
1 endpoints
/api/dashboard/associations/all-violationsCreate an HOA violation record with title, description, fine amount, and deadline.Things people ask on day one
Does Abode support mixed rental + HOA portfolios?
Who sees what in the Autopilot decision log?
How does Abode handle partial payments?
Can I export everything if I leave?
Bring your portfolio onto Abode.
We'll import rent rolls, leases, bank feeds, and open work orders in a single session — no engineering needed.