The healthcare contract layer Agentic infrastructure for healthcare administration

You bring the agents. We bring the contracts.

ANY abstracts healthcare systems of record and documents into versioned, source-aware domain contracts that agents can call.

Call the contract Explore contracts
01 Current binding 02 UB-04 + EOB/Remit 03 Box → Salesforce 04 NSA IDR workflow

What is an ANY contract?

A typed request.
A bounded response.
The evidence behind it.

Healthcare meaning is trapped across documents, data platforms, and systems of record. An ANY contract gives an agent one stable way to ask a domain question—and an explicit account of what the answer can and cannot establish.

01 / request

Typed intent

Known identifiers, effective time, context, and requested determination.

02 / response

Contracted domain

Predictable healthcare events, state, relationships, economics, and decisions.

03 / evidence

Trust envelope

Sources, observation time, conflicts, unknowns, confidence, and authority travel with the result.

No provenance. No contract.

Contract execution

Call. Resolve.
Ground. Act.

The consuming agent depends on the contract—not on a specific model, parser, queue, database, or system-of-record API. Evidence and policy cross every stage.

  1. 01Call

    An agent invokes a versioned healthcare capability with bounded intent.

  2. 02Resolve

    ANY reconciles authorized documents, data, and systems into domain state.

  3. 03Ground

    Every determination carries its sources, time, uncertainty, and limits.

  4. 04Act

    The agent continues its workflow within the returned authority and truth boundary.

EvidencePolicyAuthorityAudit

Current production binding

One workflow revealed
the platform.

A consuming system posts a case reference and Box folder reference. Encounter Lifecycle reads UB-04 and EOB/Remit evidence and returns JSON bound to a Salesforce claim model used in No Surprises Act IDR. The binding is specific. The healthcare contract is reusable.

  1. 01 / invokeConsuming system

    case_id + box_folder_id

    POST
  2. 02 / evidenceBox

    UB-04 claim form
    EOB/Remit advice

    READ
  3. 03 / contractEncounter Lifecycle

    Care event + economics
    Evidence + bounds

    RESOLVE
  4. 04 / bindSalesforce

    Claim model
    NSA IDR workflow

    APPLY
Inspect the current contract

Contract registry

Ask healthcare
a better question.

What happened? any/encounter.lifecycle@1 documents care event + economics + evidence active / private What applied? any/coverage.state@1 person + plan + time coverage state + evidence proposed / draft registry Inspect contract status, schemas, bindings, and truth boundaries.

The platform model

Bring any agent.
Keep your systems.
Depend on the contract.

Models, agent frameworks, infrastructure, documents, and systems of record can change. ANY isolates that variance behind healthcare semantics with evidence and policy attached.

The ANY contract layer
01

Systems + sources

  • Epic
  • FACETS
  • Salesforce
  • Snowflake
  • Informatica
  • Workday
  • Documents
  • File stores
02

ANY

  • Adapters
  • Resolvers
  • Domain contracts
  • Evidence envelopes
  • Policy boundaries
03

Agents + applications

  • Customer agents
  • Recovant
  • Administrative workflows
  • Consuming systems

Named systems describe the adapter surface, not universal connector availability. Availability is contract- and deployment-specific. The current Encounter Lifecycle binding uses Box and Salesforce.

Platform laws

Trust is in
the response.

Not in the confidence of the prose. Not in the reputation of the model. In the evidence, time, uncertainty, authority, and limits returned with the domain object.

Read the trust model
01

No provenance.
No contract.

02

Unknown is
a valid result.

03

Time is part
of the truth.

04

Authority is
always bounded.

Built on ANY / Recovant

The agent works the case.
ANY resolves the event.

Encounter Lifecycle resolves the care-event evidence. A Recovant agent consumes the versioned object and concentrates on No Surprises Act IDR: offers, deadlines, evidence, negotiation, and resolution.

See the first application built on ANY
01 UB-04 + EOB/Remit 02 any/encounter.lifecycle@1 03 recovant.idr.agent 04 IDR workflow

The first call

Build the agent.Call the contract.

Run a synthetic Encounter Lifecycle call, inspect the representative response, and see the truth boundary before requesting access.

Call the contract Request access