Klyniq documentation
Operate with proof, not confidence.
Build and operate bounded healthcare administrative workflows with explicit authority, narrow integrations, durable evidence, and a clear path to human attention when reality cannot be verified.
Start here
Get Klyniq ready for real work
A practical path from first sign-in to a bounded, verified workflow without giving an agent more authority than it needs.
Developers
API contracts
The stable public-facing HTTP surfaces currently intended for integration work. Internal dashboard and operator routes are deliberately excluded.
Connections
Integration boundaries
How Klyniq connects external systems without turning a connector into blanket authority.
Trust
Security and authority model
The public security model behind tenant isolation, bounded action, human approval, and evidence-backed completion.
Operations
Evidence before completion
A shared language for knowing what Klyniq can prove, what still needs verification, and when a human should take over.
Connecting a system does not grant an agent blanket permission. Tenant context, policy, workflow state, and side-effect rules stay separate.
Important real-world actions should end with durable execution evidence and, where available, readback from the authoritative provider.
Ambiguous state is not success. Klyniq keeps unresolved work visible until it is verified, reconciled, or deliberately handed to a person.