Call the contract
Menu

ANY / Developers

Start with
the contract.

Discover what your agent can ask for. Inspect the shape, the evidence, and the limits before you build.

Read the registry

01 / Public discovery

Find a capability.
Follow its descriptor.

The registry lists contract coordinates, operations, availability, bindings, and schema URLs. Read it directly from your terminal.

Terminal · public document
curl --fail --silent --show-error \
  https://any.health/.well-known/any/contracts.json

For Encounter Lifecycle, follow descriptor_url to inspect the operation and its published artifacts.

Terminal · public document
curl --fail --silent --show-error \
  https://any.health/contracts/encounter.lifecycle/1/contract.json
Open registry JSON Open ELC descriptor

02 / Inputs & outputs

Know which shape
you are reading.

Encounter Lifecycle has a working Box-to-Salesforce binding and a representative family response. The binding sends separate document extractions to a customer workflow; the family model describes a generalized care event.

Published artifactBinding request

Identify the request, folder, and case.

The binding request carries a request ID, case ID, and Box folder ID. Values below are synthetic placeholders for inspecting the published schema.

JSON · published schema example
{
  "request_id": "request-demo-001",
  "case_id": "case-demo-001",
  "box_folder_id": "synthetic-folder-001"
}

Confirm the deployed binding’s request, access requirements, and compatibility terms before integrating. This example does not invoke production. A generalized family request is not yet published.

Read the binding request schema
RepresentativeFamily response

A care event with its evidence.

The generalized shape describes platform direction. The current binding returns separate UB-04 and EOB/Remit extraction results; the customer’s Salesforce workflow reconciles them. No current binding serves this representative family response.

result
The documented care event and economics.
evidence
Source references and when they were observed.
provenance
How output fields connect to their evidence.
issues
Missing information, conflicts, and other review signals.
Read the representative response schema

See what these ideas look like in practice. The explorer uses deterministic synthetic data and does not call the private production binding.

Explore a care event

03 / Contract semantics

Status has
four dimensions.

A published schema is not a public endpoint. An active binding does not make a representative family schema a compatibility promise.

status.lifecycle

What stage is it in?

Encounter Lifecycle is active. Coverage State is proposed.

status.availability

Who can invoke it?

Encounter Lifecycle is private. Coverage State has none.

bindings[].status

What runs in a deployment?

The Box-to-Salesforce binding is production and customer-specific. Coverage State has no executable binding.

schemas[].maturity

What does this artifact represent?

The ELC request is binding; its family response is representative. Coverage State schemas are draft.

Pin the coordinate. Read the maturity.

any/encounter.lifecycle@1 identifies the contract family and major version. Before a production integration, agree the binding, exact payload, and compatibility terms. The public representative response is not a normative validator.

Read truth_boundary in each descriptor. Encounter documents can describe services, charges, and payments. Those facts alone do not establish medical necessity, coverage, clinical outcomes, or payment correctness.

04 / Private production access

Bring us the workflow
your agent needs.

We start with the administrative question and agree a binding around your sources and consuming system.

  1. 01

    Identify the evidence.

    Which documents and systems provide it, and what access is available?

  2. 02

    Define the destination shape.

    What does your agent or application need to receive to advance the workflow?

  3. 03

    Agree evidence and review behavior.

    Which fields need source support, and what should happen when information is missing or conflicting?

  4. 04

    Establish production access.

    Confirm the access agreement, customer-specific binding, and operational expectations together.

Request access

No public production invocation URL, MCP server, or authentication model is published today. A new binding requires its own agreed scope and validation.