Start a conversation
Menu

Human + AI. For the work around care.

A larger possibility for healthcare

Human time
belongs to
human care.

HumanAI

People set the purpose.
Agents carry the work.

People lead.
AI carries more of the work.

Our ambition spans US healthcare: a future where people and agents work together, with less time lost to administration and more room for human care.

Meet CareXio Explore everything ANY

01 / Featured product

CareXio.
Intent in.
Encounter out.

Fill service line capacity.

Care access, one line at a time. One capacity request, coordinated across clinical outreach, patient acquisition, and provider referrals—each with its own path to a completed encounter.

Starting with Care Gap. v0 announced 11/05/2026. First pilots forming.

Meet CareXio

One service-line intent

Capacity connects the work.

Service · Location · Capacity · Time window

  1. 01 / Clinical outreachIts own encounter
  2. 02 / Patient acquisitionIts own encounter
  3. 03 / Provider referralsIts own encounter

Illustrative coordinated model. Every path keeps its origin.

Watch intent become encounters

CareXio’s v0 demonstration uses synthetic care-gap evidence. Cross-channel orchestration and production connections are roadmap work; pilot scope is agreed separately.

02 / Everything ANY

Five capabilities. One direction.

Think at the scale
of the whole system.

Build one bounded answer at a time. Explore the platform, advisory work, and capabilities taking shape.

01

ANY Platform

The healthcare contract layer for agents. Defined data contracts and the runtime that answers them. Current production runs through a private, customer-specific binding.

Explore the platform
You bring the agents.We bring the contracts.
02

ANY Stroma*

03

ANY-1*

04

ANY Advisory

Senior, hands-on work with health systems and plans: data strategy, AI operating discipline, and the architecture decisions that precede a build.

Start a conversation
05

ANY Labs*

A planned proving ground for contract bindings across healthcare-shaped systems, built from a synthetic population. No real patient data.

Prove the binding.Before the real work.

03 / The products

The first askers of the platform

Different work.
A common foundation.

ANY products are designed to use the platform over the same interfaces as an enterprise’s own agents. Each has its own scope and stage.

Fill service line capacity. Intent in. Encounter out.

Out-of-network payment-dispute operations for providers and plans, from open negotiation through federal IDR.

The AI benefits concierge over text. Your benefits. Within reach.

Provectis*

Provider-network improvement: onboarding, credentialing, and network conversion through physician-liaison work.

Empliva*

AnyBenefits*

04 / Agents run on contracts.

The discipline behind the ambition

Big ambition.
Explicit boundaries.

A contract is a software interface for a healthcare question: a defined request, a defined response, evidence, and an explicit limit on what the answer supports.

  1. 01

    Call

    Ask a defined question.

  2. 02

    Resolve

    Read the evidence where it lives.

  3. 03

    Ground

    Return facts with their sources and limits.

  4. 04

    Act

    The consuming workflow decides the next step.

Four laws

  1. No provenance, no contract
  2. Unknown is a valid result
  3. Time is part of the truth
  4. Authority is always bounded
“A warehouse moves the data to the question. ANY moves the question to the data and sends back the answer with its receipts.”
Show the source.Keep the unknowns.Declare the limits.Read the trust model

05 / The contract catalog

Inspect the contracts

Specific questions.
Accountable answers.

Stable coordinates for the work. Read the definition, inspect the schemas, and know the maturity before you build.

Active · Private binding

What happened?

Encounter Lifecycle

Documented encounters, billing, and adjudication from UB-04 and EOB/Remit evidence.

any/encounter.lifecycle@1

Customer-specific production binding. The published family response is representative; it does not establish clinical outcome or payment correctness.

Inspect Encounter Lifecycle
Proposed · Draft schemas

Is the gap open?

Preventive Care Gap

A screening-gap verdict under a health system’s own rule, on its records, as of a requested time.

any/preventive.care-gap.state@1

In development for CareXio. No production binding or public invocation. A rule verdict is not a clinical recommendation.

Inspect Preventive Care Gap
Proposed · In design

What applied?

Coverage State

Coverage at a moment: funding type, situs, network status, and plan sponsor.

any/coverage.state@1

A proposed contract. No executable binding is available.

Inspect Coverage State

Today’s production implementation is a private, customer-specific Box → Salesforce document-extraction binding. Broader resolution and additional bindings require their own implementation and validation.

Build the agent. Call the contract.

06 / The Great Inversion

What if software
were made for
the moment?

First post · In progress

Number 5 Is Alive

Software stops being built and starts being born.

A personal note from Vishal Sibal, on childhood wonder and a future of software born on demand for the work around care.

Read the opening note

For the work ahead

Bring us the work.
Let’s make room for care.

Start a conversation

ANY supports work around care,
not the clinical practice of care.