Open pipes.
Signed outputs.

One script loads chanio, the site guide. It answers from /kb/registry.json and hands people to the right sibling site. It runs on harnesshealth.ai today; putting it on another site is a pilot conversation.

<script src="https://harnesshealth.ai/harness.js" defer></script>

Not self-serve today. The governed chat bridge at solvinghealth.com/api/chat serves the ecosystem's own sites; no API keys are issued yet. The shape below is what a governed request looks like — an attested response carries the physician NPI, the timestamp, and the document hash. Want programmatic access in a pilot? Ask on /pilot.

# illustrative — not self-serve; no API keys are issued today (see /pilot)
curl -X POST https://solvinghealth.com/api/chat \
  -H "Authorization: Bearer [API_KEY]" \
  -H "Content-Type: application/json" \
  -d '{
    "message": "Patient reports 7/10 knee pain at rest for 3 days.",
    "npi": "[REVIEWING_PHYSICIAN_NPI]",
    "require_attestation": true,
    "specialty": "orthopedic_surgery"
  }'

Connect Claude to the hosted SolvingHealth MCP server — CPT validation, prior-auth drafting, NPI lookup, patient views. Remote MCP — no install, no API key for evaluation, no local process. One click below, or paste the config into your claude_desktop_config.json manually.

Requires Claude Desktop v0.8 or later. The button opens Claude Desktop and pre-fills the harnesshealth MCP server — you approve it, and it's live.

{
  "mcpServers": {
    "harnesshealth": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote",
        "https://solvinghealth-mcp-489007249571.us-central1.run.app/mcp"
      ]
    }
  }
}

Full connector setup at: harnesshealth.ai/connect