Brellium
Brellium is an AI-powered clinical compliance platform for healthcare organizations. Its clinical AI audits 100% of a provider's clinical documentation and medical coding across every patient visit, checking notes against payor, clinical-quality, and billing requirements to catch compliance risks before they become clawbacks and to surface earned-but-unbilled revenue. It flags issues such as inaccurate MDM/E&M coding, cloned notes, and inconsistent session lengths, and gives clinical teams instant correction guidance. Brellium serves tech-enabled clinics, behavioral health, ABA, hospice, and digital-health providers, and exposes a REST API so platforms can embed chart-review and coding audits directly into their EMR or telehealth workflows.
Real signal across most facets with visible, nameable gaps — the contract exists but is thin, or the portal is good while governance and commercial terms are absent.
API Evangelist profiles Brellium the way a machine reads it — 15 machine-readable artifacts across 9 APIs, 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 — Brellium scores 50.0/100 (developing), with a separate agent-readiness read of 71/100 (agent native). 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 Brellium
Each block below is one kind of artifact we hold for Brellium. 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.
APIs 9
Each API is captured as its own OpenAPI definition — every operation, parameter, and response. This is the single most useful machine-readable description of what an API does, and it's what lets us score, lint, mock, and generate against it without asking the provider for anything.
Individual APIs this provider publishes, each with its own machine-readable definition.
Brellium Audits API
The Audits API from Brellium — 2 operation(s) for audits.
Brellium Auth API
The Auth API from Brellium — 1 operation(s) for auth.
Brellium Coding API
The Coding API from Brellium — 2 operation(s) for coding.
Brellium Documents API
The Documents API from Brellium — 3 operation(s) for documents.
Brellium Documents Multiple API
The Documents Multiple API from Brellium — 1 operation(s) for documents multiple.
Brellium Link Providers API
The Link Providers API from Brellium — 1 operation(s) for link providers.
Brellium Question Sets API
The Question Sets API from Brellium — 1 operation(s) for question sets.
Brellium Update Audits Flags API
The Update Audits Flags API from Brellium — 1 operation(s) for update audits flags.
Brellium Users API
The Users API from Brellium — 2 operation(s) for users.
Scroll within the panel for all 9 ·
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.
brellium-mcp.yml
MCP SERVEREvent Specifications 1
Not every API is request/response. AsyncAPI describes the event-driven and streaming side — the webhooks and channels — so the asynchronous half of the interface is documented the same way the synchronous half is.
AsyncAPI definitions for this provider's event-driven and streaming APIs.
Brellium Webhooks
ASYNCAPISecurity 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.
Agentic Access 1
An x-agentic-access contract marks which operations are safe for an agent to run on its own and which need a human in the loop. It is the difference between an API an agent can use and one it can use safely.
Recommended x-agentic-access execution contracts for AI agents.
Resources
Every other property we hold for Brellium — 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
Documentation 2
Reference material describing how the API behaves
Agent Surfaces 4
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 6
Pagination, idempotency, versioning, errors, and events
Access & Security 4
Authentication, authorization, and security posture
Operate 2
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
Other 1
Properties that don't map to a standard resource type
← All providers · Data indexed from github.com/api-evangelist/brellium · machine-readable index on apis.io