August
August (August Home) makes Wi-Fi smart locks, keypads, doorbell cameras, and the August Connect bridge for keyless, app-controlled home entry. Founded in San Francisco and originally backed by Bessemer Venture Partners and Uncork Capital, August was acquired by Assa Abloy and its product line is now unified with Yale Home; the two brands share the August mobile app. August does not publish a public device-control API for consumers — third-party integrations rely on community-reverse-engineered endpoints or aggregators such as Seam, and Yale/August partners use the developer.august.com portal. Its august.com storefront (hosted on Shopify) does, however, expose an agent-native commerce surface: a Universal Commerce Protocol (UCP) merchant profile at /.well-known/ucp and a hosted shopping MCP server at /api/ucp/mcp for buy-for-me agents, alongside Shopify customer-account OpenID Connect discovery.
More than an index entry, but the surface is still mostly links rather than artifacts — the cohort most likely to move a full band from modest, well-targeted work.
API Evangelist profiles August the way a machine reads it — 2 machine-readable artifacts, 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 — August scores 20.5/100 (emerging), with a separate agent-readiness read of 15/100 (agent aware). 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 August
Each block below is one kind of artifact we hold for August. 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.
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.
August Home UCP shopping MCP
MCP SERVERSecurity Posture 1
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.
Resources
Every other property we hold for August — 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 2
Portal, sign-up, and the first successful call
Agent Surfaces 3
MCP servers, agent skills, and machine-readable catalogs
Access & Security 1
Authentication, authorization, and security posture
Operate 1
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
← All providers · Data indexed from github.com/api-evangelist/august · machine-readable index on apis.io