Brightwheel
Brightwheel (mybrightwheel.com) is an all-in-one childcare and early education management platform used by childcare centers, preschools, and early-learning programs to run daily operations - attendance and check-in, digital daily sheets, tuition billing and payments, enrollment and admissions, staff/timecards, classroom (room) management, learning assessments, and real-time parent messaging and photo/video sharing. As of this catalog entry, Brightwheel does NOT publish a documented, self-serve public or partner developer API. There is no developer portal, API reference, API key signup, OpenAPI specification, or webhook documentation. The only Brightwheel API activity that is publicly acknowledged is bespoke, contract-scoped work built for individual government partners - for example a private API implemented to submit attendance and subsidy data to Iowa's childcare subsidy data system - and inbound integrations where Brightwheel pushes data into third-party products (e.g. staff timecards to Gusto for payroll). None of these expose a documented API surface that outside developers can build against. This entry is therefore an honest stub documenting the provider and its access model; no API definitions are asserted because none are publicly documented.
Index entry only — little beyond a description and a link, and nothing machine-readable enough for an agent to act on without a human reading the site first.
API Evangelist profiles Brightwheel the way a machine reads it — 1 machine-readable artifact, 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 — Brightwheel scores 13.8/100 (minimal), with a separate agent-readiness read of 0/100 (human only). 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 Brightwheel
Each block below is one kind of artifact we hold for Brightwheel. 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.
Security 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 Brightwheel — 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 1
Portal, sign-up, and the first successful call
Documentation 1
Reference material describing how the API behaves
Build 1
SDKs, sample code, and the tooling you integrate with
Access & Security 1
Authentication, authorization, and security posture
Commercial 1
Pricing, plans, and the legal terms of use
Company 3
The organization behind the API
← All providers · Data indexed from github.com/api-evangelist/brightwheel · machine-readable index on apis.io