Need help with your APIs? I offer API discovery, governance & evangelism services. Explore services →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Sword

Sword Health is a digital health company delivering AI-powered virtual care for musculoskeletal (MSK) pain, pelvic health, and injury prevention. Founded in 2015 in Portugal by Virgilio Bento, Sword pairs licensed physical therapists with motion-sensor and computer-vision technology so members can complete clinically supervised physical therapy from home. Its platform spans an enrollment platform, a treatment platform, a mobile application backed by a mobile API, a file-exchange platform for enterprise clients, and an AI care system. Sword serves 1,000+ enterprise and health-plan clients across three continents, is backed by investors including General Catalyst, Khosla Ventures, Founders Fund, and Transformation Capital, and maintains SOC 2 Type 2, HITRUST, ISO 13485, HIPAA, GDPR, and Cyber Essentials compliance. Sword does not currently publish a public developer API program; this profile captures its identity, status, security, and compliance surface.

human only

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.

Kin Score

API Evangelist profiles Sword 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 — Sword scores 23.6/100 (emerging), 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 Kin Score How this is scored →
scored 2026-07-27 · rubric v0.5
Composite quality — 23.6/100 · emerging
Contract Quality 0.0 / 25
Developer Ergonomics 0.0 / 20
Commercial Clarity 7.4 / 20
Operational Transparency 4.1 / 13
Governance 0.0 / 12
Discoverability 6.8 / 10
Regulatory · Health 8.1 / 15
Agent readiness — 0/100 · human only
Machine-Readable Contract 0 / 18
Agentic Access Contract 0 / 15
MCP Server 0 / 12
Machine-Readable Auth 0 / 10
Idempotency 0 / 9
Stable Error Semantics 0 / 8
Request/Response Examples 0 / 7
Rate-Limit Signaling 0 / 7
Typed Event Surface 0 / 6
Agent Skills 0 / 5
Well-Known Catalog 0 / 4
Consent & Bot Identity 0 / 3

How we profile Sword

Each block below is one kind of artifact we hold for Sword. 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 3

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.

Sword Domain Security

TLSv1.3 · DMARC

SECURITY

Sword Vulnerability Disclosure

Hackerone · contact published

SECURITY

Sword Trust Center

SOC 2 Type 2, HITRUST, ISO 13485:2016, HIPAA, HITECH, GDPR, Cyber Essentials, PIPEDA

SECURITY

Resources

Every other property we hold for Sword — 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.

Design & Contract 1

Pagination, idempotency, versioning, errors, and events

Build 1

SDKs, sample code, and the tooling you integrate with

Operate 1

Status, limits, changes, and where to get help

Commercial 2

Pricing, plans, and the legal terms of use

Company 1

The organization behind the API

← All providers · Data indexed from github.com/api-evangelist/sword · machine-readable index on apis.io