Connect systems without breaking evidence.

Quickstart

Begin with the integration boundary.

1. Identify the tenant and project.Application access is authenticated and tenant-scoped.
2. Register the source.Keep original identity, version and evidence before transformation.
3. Validate the result.Use supported runtime contracts and retain warnings or uncertainty.

API

Currently verified public contracts

Additional application APIs are authenticated internal product contracts and are not represented here as a public API.

.zmx Format

Canonical ZemriX object package

Historical read/import adapters remain isolated from the canonical .zmx writer and new ZemriX behavior.

Authentication

Fail closed across tenant boundaries.

Sessions, protected routes and organization membership are enforced by the application runtime. Credentials and sensitive application data must never enter marketing analytics.

Examples

Evidence-first response check

fetch("https://app.zemrix.cloud/api/zemrix/health")
  .then((response) => {
    if (!response.ok) throw new Error("health boundary unavailable");
    return response.json();
  });

Changelog

ZemriX V1

The current production baseline uses `.zmx` as the canonical format and preserves legacy compatibility only at explicit boundaries.

Status / Trust

Verify before you integrate.

Use the health boundary for service status. Security, provenance and compatibility claims remain limited to published, testable product behavior.