Build on the HIPAA-compliant agent.
A REST API with FHIR and HL7 support, real-time webhooks, and connectors to the EHRs and CRMs you already use — wrapped in encryption, audit logging, and a signed BAA.
REST API
Clean, predictable JSON endpoints for messaging, scheduling, patients, and documents — with examples to get going fast.
FHIR & HL7
Standards-based interoperability so Phiclaw reads and writes to your EHR the way healthcare data is meant to move.
Webhooks
Subscribe to real-time events — new messages, bookings, intake submissions — and react in your own systems instantly.
HIPAA & BAA
Encryption in transit and at rest, audit logging, PHI minimization, and a signed BAA before any protected data flows.
Keys & OAuth
Scoped API keys and OAuth for partner apps, with granular permissions and easy rotation.
Reliable & observable
Sensible rate limits, idempotency, and status visibility so integrations stay predictable in production.
A request looks like this.
Authenticate with a scoped key, call a resource, get JSON back. Full reference and client examples are shared when you're granted access.
# Send a message on behalf of a practice curl https://api.phiclaw.ai/v1/messages \ -H "Authorization: Bearer $PHICLAW_API_KEY" \ -H "Content-Type: application/json" \ -d '{ "patient_id": "pat_8fk2", "channel": "sms", "body": "Your visit summary is ready." }'
How PhiClaw checks eligibility and gets claims paid, through Stedi.
PhiClaw connects to Stedi, a HIPAA-compliant healthcare clearinghouse API with 3,681 payers listed in its November 10, 2026 public directory, including UnitedHealthcare, Aetna, Cigna, Humana, Anthem and Blue Cross Blue Shield plans, Medicaid and TRICARE. Your AI employee calls these APIs for you from your EHR, and every request and response is logged on the patient's account.
Browse the complete payer directory, IDs and transaction support. Support and enrollment requirements differ by payer.
What happens to a claim
- Before the visit. A real-time eligibility check confirms the plan is active and pulls copay, deductible and coinsurance. A COB check flags secondary coverage.
- After the visit. The AI builds the 837 claim from the signed note: CPT and ICD-10 codes, modifiers, place of service, rendering and billing NPI. A person approves it, then it goes to the payer through Stedi.
- Minutes later. The 277CA acknowledgment says accepted or rejected. Rejections (a wrong member ID, a missing modifier) are fixed and resubmitted the same day.
- While it is pending. Real-time 276/277 status checks run on a schedule, so nothing sits unnoticed.
- When it is paid. The 835 ERA is posted to the patient's ledger and matched to the EFT deposit. Denials go into the appeal queue with the reason code (with Insurance claims & RCM, $300/mo plus $0.30 per submitted claim).
# What PhiClaw sends to Stedi's real-time eligibility API (simplified) POST https://healthcare.us.stedi.com/2024-04-01/change/medicalnetwork/eligibility/v3 { "tradingPartnerServiceId": "87726", "provider": { "organizationName": "Your Practice", "npi": "1999999984" }, "subscriber": { "firstName": "Jane", "lastName": "Doe", "memberId": "U1234567", "dateOfBirth": "19800101" }, "encounter": { "serviceTypeCodes": ["30"] } } # 87726 is UnitedHealthcare's payer ID. The JSON reply carries # plan status, copay, deductible and coinsurance, and PhiClaw # writes it to the patient's chart before the visit.
Insurance claims & RCM is a $300/month add-on plus $0.30 per submitted claim. The monthly fee is included in the engineer plan; per-claim charges still apply. Stedi's API keys stay on our servers and are never sent to the browser. Fields above are an example; real requests use the patient's actual plan details under your signed BAA.