Aptly
Aptly is the AI operations layer for property management, built by Invisible Apps, Inc. It unifies resident and owner communication (calls, texts, emails, and chat) with board-based workflows, automation, and AI agents that handle leasing inquiries, maintenance requests, and around-the-clock resident communication, and it syncs bidirectionally with property management systems including Yardi, RealPage, Entrata, and AppFolio. The Aptly Core API (https://core-api.getaptly.com) gives external systems and AI agents direct read/write access to boards, cards, contacts, tasks, inboxes, calendars, files, and knowledge documents using a per-company API key, and Aptly ships an official hosted MCP server (https://mcp.getaptly.com/mcp) as the recommended way to connect LLMs. A separate Portal API powers the rental-application screening portal.
Real signal across most facets with visible, nameable gaps — the contract exists but is thin, or the portal is good while governance and commercial terms are absent.
API Evangelist profiles Aptly the way a machine reads it — 19 machine-readable artifacts across 15 APIs, pulled from the provider's own public surface and indexed so a developer, an analyst, or an AI agent can evaluate it against every other provider on the network.
Every provider in the network is reduced to the same set of machine-readable artifacts — OpenAPI contracts, event specifications, GraphQL schemas, runnable collections, pricing and rate-limit signals, security posture, OAuth scopes, and the agent surfaces (MCP servers and skills) that let software drive the API on its own. We profile them because the interface is the part of a company you can actually inspect: it is a truer signal of what a provider does than any marketing page. From those artifacts we compute the Kin Score — Aptly scores 49.7/100 (developing), with a separate agent-readiness read of 72/100 (agent native). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.
Kin Score
This is the API Evangelist rating — a single, repeatable read computed from the artifacts on this page. Green fill is points earned; the red track is points possible, so every bar shows earned-versus-possible at a glance.
Kin Score
How this is scored →scored 2026-07-27 · rubric v0.5
How we profile Aptly
Each block below is one kind of artifact we hold for Aptly. For each we say what it is and why it earns a place in the profile, then list every one we've indexed — capped at two rows, scroll within the panel for the rest.
APIs 15
Each API is captured as its own OpenAPI definition — every operation, parameter, and response. This is the single most useful machine-readable description of what an API does, and it's what lets us score, lint, mock, and generate against it without asking the provider for anything.
Individual APIs this provider publishes, each with its own machine-readable definition.
Aptly App API
The App API from Aptly — 2 operation(s) for app.
Aptly Board API
The Board API from Aptly — 12 operation(s) for board.
Aptly Boards API
The Boards API from Aptly — 1 operation(s) for boards.
Aptly Cards API
The Cards API from Aptly — 6 operation(s) for cards.
Aptly Company API
The Company API from Aptly — 1 operation(s) for company.
Aptly Contacts API
The Contacts API from Aptly — 5 operation(s) for contacts.
Aptly Email API
The Email API from Aptly — 2 operation(s) for email.
Aptly Files API
The Files API from Aptly — 2 operation(s) for files.
Aptly Inboxes API
The Inboxes API from Aptly — 1 operation(s) for inboxes.
Aptly Knowledge API
The Knowledge API from Aptly — 2 operation(s) for knowledge.
Aptly RoutingGroups API
The RoutingGroups API from Aptly — 4 operation(s) for routinggroups.
Aptly Schema API
The Schema API from Aptly — 1 operation(s) for schema.
Aptly Tasks API
The Tasks API from Aptly — 3 operation(s) for tasks.
Aptly Templates API
The Templates API from Aptly — 2 operation(s) for templates.
Aptly Users API
The Users API from Aptly — 2 operation(s) for users.
Scroll within the panel for all 15 ·
MCP Servers 1
Model Context Protocol servers expose these APIs directly to AI agents. We profile them because agent-native access is the fastest-growing way this provider's capabilities actually get used.
Model Context Protocol servers that expose these APIs to AI agents.
aptly-mcp.yml
MCP SERVERSecurity Posture 2
Authentication, domain security, vulnerability disclosure, and trust-center signals — the evidence that a provider takes security seriously enough to document it. We profile it because you can't govern what you can't see.
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Agentic Access 1
An x-agentic-access contract marks which operations are safe for an agent to run on its own and which need a human in the loop. It is the difference between an API an agent can use and one it can use safely.
Recommended x-agentic-access execution contracts for AI agents.
Resources
Every other property we hold for Aptly — documentation, portals, status pages, policies, and corporate surface — grouped by the job it does, following the integrator's arc from getting started to running in production.
Get Started 3
Portal, sign-up, and the first successful call
Documentation 3
Reference material describing how the API behaves
Agent Surfaces 4
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 6
Pagination, idempotency, versioning, errors, and events
Build 1
SDKs, sample code, and the tooling you integrate with
Access & Security 2
Authentication, authorization, and security posture
Operate 3
Status, limits, changes, and where to get help
Commercial 3
Pricing, plans, and the legal terms of use
Company 2
The organization behind the API
Other 1
Properties that don't map to a standard resource type
← All providers · Data indexed from github.com/api-evangelist/aptly · machine-readable index on apis.io