Zdravo exposes an HTTP API, MCP server, published CLI and SDK packages, and a developer-mode Chrome extension. Each entry point has a distinct scope; connecting one does not automatically govern all actions taken by an external agent.
Use the HTTP and OpenAPI surface for supported Zdravo operations; authentication and authorization are route-specific.
API docsConnect supported MCP clients to tools exposed by the published zdravo-mcp server. This does not intercept a client's other tools.
MCP guideInstall the published zdravo-cli package for terminal access to Zdravo APIs. CLI commands do not intercept an external agent's other tools.
Install CLIInstall the published zdravo-sdk package for typed application access to Zdravo APIs. It does not intercept agent actions outside those requests.
Install SDKRuntime model
Developer integrations are useful because they enter the same governance path. Protected actions are bound to organization and governed agent identity, evaluated against policy, and recorded as inspectable decision and observation state.
Inspect the architecture