Read/write Patient, Observation, Communication, Flag resources
Build on Piu. Model API, RAG, agents.
A developer surface for the platform — model selection, tenant-scoped document ingest, and programmatic agent creation. Standards-based. Isolated per tenant.
FHIR R4 · X12 EDI · NCPDP · SMART on FHIR · OAuth 2.1 · BYO pathway as YAML
Model selection & hot-swap
Choose the model per tenant or per agent. Swap at runtime without rebuilding pathways or losing cohort context. Cost, latency, and capability trade-offs are yours to make.
Early accessPOST /v1/tenants/{id}/model
{
"provider": "anthropic",
"model": "claude-sonnet-4-6",
"fallback": "claude-haiku-4-5"
}Tenant-scoped RAG ingest
Upload documents to your tenant's isolated vector index. Formularies, protocols, benefit rules, dietary standards — whatever Piu should ground its answers in. Chunking, embedding, and retrieval are managed.
Early accessPOST /v1/tenants/{id}/rag/ingest
Content-Type: multipart/form-data
file: formulary_2026_q3.pdf
namespace: "benefits"
ttl: "90d"Agent builder (no-code + API)
Build agents by describing them in plain language, or programmatically via the API. Supply reference docs, set guardrails, and deploy white-labeled under your brand. Guardrail validation runs before publish — human sign-off only if flagged.
Early accessPOST /v1/tenants/{id}/agents
{
"name": "Post-discharge CHF",
"description": "Daily check-in...",
"docs": ["proto_chf_v2.pdf"],
"guardrails": "clinical_default",
"publish": "draft"
}Standards & auth
Claims and remittance for payer integration
Pharmacy benefit and formulary exchange
App launch from any EHR patient chart
Token-based auth with PKCE, scoped per tenant
Versioned YAML care pathways, diffable, git-native
HIPAA-aligned · BAA-ready · SOC 2 in progress · Per-tenant Postgres RLS · Isolated vector indexes · Model choice does not affect data isolation. Read the security brief →
Early access · select design partners · Platform overview →
Request early access →
Piu Health