Show the source.
Material facts should be traceable to the evidence that supports them.
The healthcare contract layer for agents
You bring the agents. We bring
the contracts.
A consistent way to work with healthcare documents and systems—with defined inputs, useful results, and the evidence behind them.
Agentic infrastructure for healthcare administration.
INSIDE A CONTRACT CALLThe work behind the result.
ILLUSTRATEDEXECUTION
ANY kernelCONTRACT RUNTIME
any/encounter.lifecycle@1Box → Salesforce bindingDocumented factsStructured outputReady for the next step
01 / 05 · Call the contractILLUSTRATION
Start with the case and the evidence your workflow is authorized to use.
WORKFLOW → EVIDENCE → CONTRACTSelect any layer to inspect it.
A private ELC binding, illustrated. No production call.
Current production bindingUB-04 + EOB/RemitBox → SalesforcePrivate · Customer-specific · NSA IDR
What you build on
Healthcare context.
Ready for your agent.
Every new healthcare agent faces familiar work: find the records, interpret the documents, reconcile the facts, and fit the result to a workflow.
ANY is building the contract layer for healthcare AI: reusable domain meaning, traceable evidence, and explicit boundaries around what an agent can know and do. Contracts carry that context across documents, systems, and workflows.
Typed requestDomain resultEvidence + limits
From execution to understanding
For the agent, a result.
For the person, a reason.
A structured result gives an agent something to work with. The evidence gives a person something to inspect.
THE AGENT ASKS“What was documented as paid?”
THE PERSON ASKS“Which source supports that?”
Explore an encounter with complete, missing, or conflicting evidence. Select a fact to see its source, or switch to JSON to inspect the response an agent could consume.
Go deeper into Encounter LifecycleThis synthetic example illustrates the broader ELC contract. The current binding returns separate extraction envelopes; Salesforce combines them for its workflow.
ELC / ENCOUNTER LIFECYCLEEXPLORE THE RESULT
The contract catalog
Start with what happened.
Build toward what applied.
01 / WHAT HAPPENED?
Encounter Lifecycle
Feed your agents care events—not documents. Resolve encounter and payment evidence into a shape a consuming workflow can use.
any/encounter.lifecycle@1Active · Private binding
02 / WHAT APPLIED?Coverage State
A proposed contract for who is covered, under which plan, at what time, and through which network.
any/coverage.state@1Proposed · In design
Agents run on contracts.
Keep your systems.
Depend on the contract.
A common foundation for healthcare AI governance. Domain meaning, evidence, time, uncertainty, and authority travel with the work—even as agents, models, and source systems change.
YOUR AGENTS
ANY CONTRACT LAYER
SYSTEMS + DOCUMENTS
Platform vision and intended adapter surface. Today’s production implementation is a private, customer-specific Box–Salesforce document-extraction binding. The generalized ELC response is representative; Coverage State is draft. Additional integrations, shared resolution, and governance controls require deployment-specific implementation and validation.
Keep the unknowns.
Missing and conflicting evidence need an explicit place in the response.
Declare the limits.
A result should make clear what it supports and where review belongs.
Meet BenefitsCHAT
Your benefits.
Within reach.
Working product
BenefitsCHAT is an AI benefits concierge over text. Help people understand their plan, navigate their care network, and reach the right help. Turn benefits communication into a conversation that supports member engagement and a clearer next step.
Explore BenefitsCHATMeet Recovant
Payment disputes.
A clearer path to resolution.
In active development
Recovant is being built to help health plans and providers manage out-of-network payment disputes—from open negotiation through Federal Independent Dispute Resolution (IDR) under the No Surprises Act (NSA).
Explore RecovantMake your first call
Build the agent.
Call the contract.
Explore the synthetic example, inspect the artifacts, then talk with us about a production binding.