Flossy
Flossy is a Santa Monica, California healthcare technology company that builds AI agents ("AI coworkers") for dental practices, veterinary clinics and med spas. Its named agents cover front-office and revenue-cycle work: Fiona handles inbound and outbound patient communication and scheduling across phone, SMS and web chat; Betsy scores call-center quality and marketing performance; Michael captures insurance, verifies benefits and surfaces billing insights; and Reid forecasts revenue and optimizes schedule capacity and staffing. FlossyHQ is the operator console the practice works in, and Agent Builder lets practices assemble custom agents. Founded in 2020 by Miles Beckett and Steve Seigel, Flossy began as a pay-as-you-go dental care marketplace and has since repositioned around agentic automation for practice operations. Flossy publishes no public developer program, API reference or machine-readable specification; the one publicly reachable first-party integration surface is the embeddable Fiona web-chat widget.
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 Flossy the way a machine reads it — 3 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 — Flossy scores 15.4/100 (emerging), with a separate agent-readiness read of 3/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.
Why this profile is thin
Flossy ships AI agents only as an end-user product for practices — there is no developer portal, API reference or spec anywhere on its surface: /developers, /developer, /api and /docs all 404, developer.flossy.com and docs.flossy.com do not resolve, api.flossy.com is a dangling CNAME to a Heroku Private Space with no public A record, and the one live API host (scheduler-api.flossy.com) answers 200 on its root but 404s every OpenAPI/Swagger/docs path and requires an x-api-key.
This is an honest zero, not a gap in our research. Flossy does not appear to expose an API, so there is nothing here for us to index and nothing for them to fix.
What we probed
https://www.flossy.com/developers→ HTTP 404https://www.flossy.com/docs→ HTTP 404https://scheduler-api.flossy.com/openapi.json→ HTTP 404https://www.flossy.com/.well-known/agent-card.json→ HTTP 404https://hq.flossy.com/fiona-widget.js→ HTTP 200
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-08-17 · rubric v0.11.0
Put this on your own site. The badge is drawn live from Flossy's current Kin Score — paste it once and it updates itself every time the score is recomputed. It follows your visitor's light or dark setting, and it links back here so anyone who sees it can read the full breakdown.
<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/flossy/"
title="Flossy on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/flossy.svg"
alt="Flossy Kin Score — API readiness rating by API Evangelist" width="150" height="150" loading="lazy">
</a>[](https://providers.apievangelist.com/providers/flossy/)<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/flossy/"
title="Flossy on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/flossy/card.svg"
alt="Flossy Kin Score — API readiness rating by API Evangelist" width="340" height="120" loading="lazy">
</a>More shapes, themes and sizes → · Score as JSON · How badges work
How we profile Flossy
Each block below is one kind of artifact we hold for Flossy. 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.
Pricing Plans 1
Pricing is part of the interface. Machine-readable plans tell you what a tier costs and includes before you commit — one of the six things the Kin Score reads for commercial clarity.
Published pricing tiers and plan structures.
Flossy Plans Pricing
PLANSRate Limits 1
Rate limits are the difference between a demo that works and a production integration that doesn't fall over. Publishing them is an operational-transparency signal — and a hard requirement for any agent that plans its own throughput.
Documented rate limits and quota policies.
Flossy Rate Limits
RATE LIMITSSecurity 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 Flossy — 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
Agent Surfaces 1
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 1
Pagination, idempotency, versioning, errors, and events
Access & Security 1
Authentication, authorization, and security posture
Operate 2
Status, limits, changes, and where to get help
Commercial 3
Pricing, plans, and the legal terms of use
Company 4
The organization behind the API
← All providers · Data indexed from github.com/api-evangelist/flossy · machine-readable index on apis.io
This is an independent, third-party profile of Flossy, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.
The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.
Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.
info@apievangelist.com
·
Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and
you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.