claims.searchadaptix-billingSearch active claims with live risk scoring, tenant-scoped.
WIRED READPHI
Opening AdaptixCore
Opening the page you asked for.
DEVELOPERS · MCP TOOL BROKER
Give the agent domain tools, not a database and a prayer.
The Adaptix MCP Tool Broker exposes typed operational intents behind server-side authorization. The model gets the tools the verified caller may use, writes remain approval-gated, PHI stays classified, and an unavailable downstream adapter returns a typed failure instead of fabricated data.
Built around the operation, not the software menu
TOOL BROKER
MCP 2025-06-1825tool contracts
20read tools
5approval writes
4wired reads
tools/list -> verify caller -> resolve policy -> filter catalog tools/call -> validate schema -> enforce PHI class -> resolve policy -> adapter | typed failureUnknown or unavailable is a real state. It is never rewritten as success.
THE SHORT ANSWERS FIRST
What you can build against, today.
What can developers integrate?
Typed domain tools over the operational platform — claims, charts, credentials, scheduling, documents, analytics, and audit — exposed through the Adaptix MCP Tool Broker rather than raw database or UI automation.
What is available now?
4 read tools are wired to live adapters today. Every other registered read returns a typed MCP_TARGET_UNAVAILABLE until its adapter ships — the manifest below marks each tool's real state, and nothing unavailable is marketed as available.
How is access authorized?
Server-side. Caller identity is verified outside the prompt, policy resolution decides tool visibility and execution per caller, and unknown or failed policy resolves to denial.
MCP and the API — what's the relationship?
The broker is an MCP server in front of the platform's own authorized service APIs. It adds no privileges: a tool call succeeds only where the same caller's API request would.
Read-only vs write?
Reads dominate the catalog (20 tools). The 5 write contracts are prepare/submit pairs: preparing returns a pending-approval id and changes nothing downstream.
What requires approval?
Every write execution. A prepared claim correction, message, or statement becomes real only after human approval — model intent alone never executes.
Where are docs and examples?
The tool manifest and connection model on this page are the current public reference. A hosted docs portal is not published yet — for integration access and a working walkthrough, talk to us directly.
THE BOUNDARY MATTERS MORE THAN THE CHAT WINDOW
Four rules the model does not get to negotiate.
01
Identity is server-derived
The broker does not accept prompt-supplied identity as authorization. Tool visibility and execution are resolved against verified caller context.
02
Policy failures deny
Policy timeout, DNS failure, malformed policy response, or unavailable authorization resolves closed rather than manufacturing access.
03
Writes require approval
Write execution is disabled by default and the write contracts are approval-gated. Prepared actions do not become executed actions merely because a model requested them.
04
PHI is classified at the broker boundary
Tools that can traverse PHI are marked explicitly so the broker can enforce the caller's permitted data class before the downstream request is attempted.
TOOL MANIFEST · TYPED CONTRACTS
The catalog says what exists. The adapter says what is live.
4 read adapters are marked wired in the current broker contract. Other registered reads must fail as typedMCP_TARGET_UNAVAILABLE until their target adapter is actually available.claims.getadaptix-billingFetch a single claim's live risk profile by claim id.
WIRED READPHI
claims.get_statusadaptix-billingReturn the current payer claim-status observation for a claim.
WIRED READ
claims.get_submission_historyadaptix-billingReturn the submission history for a claim (837 lifecycle).
TYPED READPHI
claims.get_denial_historyadaptix-billingReturn denial history and CARC/RARC codes for a claim.
TYPED READPHI
eligibility.get_resultadaptix-billingReturn the latest 270/271 eligibility result for a patient.
TYPED READPHI
era.get_reconciliation_statusadaptix-billingReturn ERA/835 remittance reconciliation status for a batch or deposit.
TYPED READ
billing.get_summaryadaptix-billingReturn the tenant billing summary for AR, aging, and KPIs.
TYPED READ
billing.get_exception_summaryadaptix-billingReturn the tenant billing exception summary for queues, blockers, and aging.
TYPED READ
epcr.get_chart_statusadaptix-epcrReturn the current state of a specific chart.
WIRED READPHI
epcr.get_completion_gapsadaptix-epcrReturn field-level completion gaps blocking chart lock.
TYPED READPHI
epcr.get_quality_findingsadaptix-epcrReturn NEMSIS quality-validation findings attached to a chart.
TYPED READPHI
credentials.get_statusadaptix-workforceReturn the current credential status for a user.
TYPED READ
credentials.get_expiringadaptix-workforceReturn credentials expiring inside the requested window.
TYPED READ
scheduling.get_user_scheduleadaptix-workforceReturn the caller's upcoming tenant-scoped schedule.
TYPED READ
scheduling.get_open_shiftsadaptix-workforceReturn open shifts the caller is credentialed and eligible to claim.
TYPED READ
documents.get_statusadaptix-billingReturn delivery status of a generated document.
TYPED READ
documents.search_authorizedadaptix-billingSearch documents the caller is authorized to see.
TYPED READ
analytics.get_operational_summaryadaptix-coreReturn the operational summary for the tenant.
TYPED READ
audit.search_authorized_activityadaptix-coreSearch authorized audit activity for the tenant.
TYPED READ
claims.prepare_correctionadaptix-billingDraft a claim correction and return a pending-approval id; does not submit.
APPROVAL WRITEPHI
claims.submit_correctionadaptix-billingSubmit a previously prepared claim correction after human approval.
APPROVAL WRITEPHI
communications.prepare_messageadaptix-communicationsDraft an outbound message and return a pending-approval id; does not send.
APPROVAL WRITEPHI
communications.send_approved_messageadaptix-communicationsSend a previously prepared, human-approved message.
APPROVAL WRITEPHI
documents.prepare_statementadaptix-billingPrepare a patient statement or billing document; does not deliver it.
APPROVAL WRITE
CONNECTION MODEL
The client asks. The server decides what that client is allowed to know exists.
01
Authenticated client
Caller identity originates outside the prompt.
02
MCP broker
Validates tool schema and caller context.
03
Policy resolution
Server-side authorization decides visibility and execution.
04
Domain adapter
Only the authorized target receives the request.
05
Typed result
Success, denied, PHI-not-permitted, policy-unavailable, or target-unavailable remains explicit.
POLICY RESOLUTION
POST /api/v1/ai/policy/resolve/toolALLOW -> tool remains visible / executable DENY -> request stops POLICY_UNAVAILABLE -> request stops PHI_NOT_PERMITTED -> request stops MCP_TARGET_UNAVAILABLE -> typed downstream failure
BUILD AGAINST THE CONTRACT THAT EXISTS