InBrace
InBrace was the lingual orthodontics brand of Swift Health Systems, Inc., an Irvine, California medical-device company co-founded in 2012 by orthodontists John Pham and Hongsheng Tong. Its patented INBRACE Smartwires were programmed from digital scans of a patient's teeth and bonded behind the teeth, moving teeth continuously without relying on patient compliance; the product reached market in 2016 and was sold to orthodontic practices through a doctor-facing case-submission portal at portal.inbrace.com rather than through any public developer program. The company raised roughly $70 million in total, including a $45 million Series C led by Vivo Capital with Novo Holdings and venBio Partners in 2019. InBrace ceased operations in April 2025, citing tightening capital markets and slower-than-expected adoption, leaving providers with cases mid-treatment. Its intellectual property, production equipment and manufacturing assets were acquired by orthodontist Dr. Scott Schwartz, who relaunched the technology in August 2025 as InSmile Braces — an independent company operated by Lorelli Technologies and explicitly separate from InBrace. As of this profile inbrace.com and portal.inbrace.com 301-redirect wholesale to insmilebraces.com, so no InBrace-origin content is served from any host. InBrace never published an API, SDK, developer portal or machine-readable specification, and none is served today.
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 InBrace 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 — InBrace scores 4.1/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.
Why this profile is thin
Swift Health Systems, Inc. (InBrace) ceased operations in April 2025 and every path on inbrace.com — apex, /.well-known/*, /openapi.json, /llms.txt, /docs, /api — now answers HTTP 301 into insmilebraces.com, the site of InSmile Braces, the separate company that bought the IP; the surviving portal host is a login-gated React app whose only backend is an internal /api/ path, so there is no InBrace-owned contract left to read.
This is an honest zero, not a gap in our research. InBrace 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://inbrace.com/→ HTTP 301https://inbrace.com/openapi.json→ HTTP 301https://inbrace.com/.well-known/agent-card.json→ HTTP 301https://www.insmilebraces.com/openapi.json→ HTTP 404https://www.insmilebraces.com/llms.txt→ HTTP 404https://portal.insmilebraces.com/openapi.json→ HTTP 401
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-24 · rubric v0.12.1
Put this on your own site. The badge is drawn live from InBrace'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/inbrace/"
title="InBrace on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/inbrace.svg"
alt="InBrace Kin Score — API readiness rating by API Evangelist" width="150" height="150" loading="lazy">
</a>[](https://providers.apievangelist.com/providers/inbrace/)<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/inbrace/"
title="InBrace on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/inbrace/card.svg"
alt="InBrace 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 InBrace
Each block below is one kind of artifact we hold for InBrace. 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 InBrace — 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.
Access & Security 1
Authentication, authorization, and security posture
Company 1
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/inbrace · machine-readable index on apis.io
This is an independent, third-party profile of InBrace, 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.