honest about what's live today

Eighteen integrations. Three statuses.

Every connector we ship is in one of three states — LIVE in production with paying customers, BETA with at least one design partner, or COMING because we've scoped it but haven't built it. No vapourware.

9
live
running in production today
6
beta
working — not yet load-tested for every customer
2
coming
scoped, will ship when a customer needs it
EHR
4
T
LIVE

Tebra

Pull schedule, post payments, write claim notes back.

Playwright agent against Tebra portal. Nightly schedule pull, payment post-back, claim notes write-back. Native API on the roadmap.

V
BETA

Valant

Behavioral-health EHR. Portal automation, no API.

Read-only Playwright today for practices on Valant. Write-back paths in design — Valant has limited public API surface.

M
LIVE

Mahler

Nightly EOB poster, claim status, credentialing.

Native API + Playwright fallback. 41 EOBs posted last week against Mahler. Daily-rhythm report drops at 6am ET.

A
BETA

Athena

athenahealth — scoping completed, scaffold in.

Integration scaffolded against AthenaOne API. Not posting yet — graduates to LIVE after first paying customer on Athena.

Clearinghouse
5
Av
LIVE

Availity

Primary 270/271 path. Zero-cost real-time eligibility.

Availity Essentials portal via Playwright + 270/271 EDI route. Our default for eligibility — $0 marginal cost where the payer supports it.

S
LIVE

Stedi

Trading-partner X12 path for payers Availity can't reach.

API path coded against Stedi. Currently paused for cost reasons — Availity covers most of our payer mix. Trading-partner API ready when we need a payer Availity doesn't have.

pV
BETA

pVerify

Alternate eligibility route for tricky payers.

Wired into the eligibility router as a third option. Used as a fallback when Availity returns 'payer not supported'.

Tz
COMING

Trizetto

Direct Trizetto submission (Tebra's clearinghouse).

Tebra's claim path lands at Trizetto today. Direct Trizetto submission is on the roadmap — we ride the Tebra path until we hear demand to swap.

W
COMING

Waystar

Larger-clinic clearinghouse, scoped not built.

Not connected. We bring it up the day a customer asks for it. Scoping doc exists.

Voice
2
Tw
LIVE

Twilio

Six lines for Echo. Inbound + outbound + SIP trunk.

Six Twilio numbers wired to four voice personas (Ava, Niya, Sarah, Roger). BYOC SIP available for enterprise customers.

EL
LIVE

ElevenLabs

Voice models behind every Echo persona.

Voices locked per persona. TTS + STT with conversational agents. TCPA-aware call flow on outbound.

AI
1
C
LIVE

Anthropic Claude

Classifier, drafter, brain behind every workflow.

Claude Opus + Sonnet 4.5 across denial classification, appeal drafting, inbox triage, meeting summarisation. Token budgets enforced per workspace.

Productivity
2
MS
BETA

Microsoft Graph

Outlook mail + calendar + Teams transcripts.

OAuth flow live for Outlook read. Calendar + Teams transcripts ramping with the 4-app split (Workspace / Mail / Calendar / Meetings). Full LIVE after tenant MFA cleared.

G
BETA

Google Workspace

Gmail OAuth + Calendar + Drive read.

Gmail OAuth in production. Calendar + Drive on the same scope. Workspace-wide admin install path on the roadmap.

Billing
1
St
LIVE

Stripe

Checkout + customer portal + signed webhooks.

Shipped in the billing milestone. Self-serve subscribe, plan changes through the portal. Webhooks signed; we never trust unsigned events.

Compliance
1
DS
BETA

DocuSeal

Self-hosted BAA + agreement signatures.

Bonterms BAA template + DocuSeal self-host on EC2. Counter-signed PDF lands in the workspace's audit log. AWS BAA already signed, end-to-end coverage on day one.

Infrastructure
1
aws
LIVE

AWS

HIPAA-grade infra. BAA on file with AWS.

AWS BAA signed. EC2 + Lambda + S3 (per-tenant prefix) + SES for system mail. KMS-encrypted at rest, TLS 1.2+ in transit. SOC 2 Type II in progress.

how we read these badges

The bar for LIVE is high on purpose.

  • LIVE means at least one paying customer is using this connector in production this week. We have the logs.
  • BETA means it's wired, it works, but we either have only one design partner on it or we're still hardening the unhappy-path. If you're comfortable being the second customer, talk to us.
  • COMING means we've scoped the work and we know exactly what it takes. We don't build it until a customer signs a contract that needs it. Lean roadmap by design.
missing one?

Need a connector we don't list?

We add real integrations only when a customer signs a contract that needs them. If you have one, write to us — we ship fast when the use-case is real.

Try Verify free Email hello@getmaxglobal.com