Synthetic contract sandbox

Wire your client against stable fixtures.

These public, read-only fixtures use the exact approved post-gate response shapes. They contain no tenant data, ignore Authorization headers, never call Platform3, and are not evidence that production report routes or upstream gates are released.

Sandbox boundary: only the request shapes below resolve. The candidate-list cursor selects its terminating second fixture page, while a testKind other than mastery_gate returns an empty terminal page to demonstrate server-enforced filtering. Other query parameters, the materialize body, and headers are accepted for client-shape testing but do not select data or trigger writes. Use this surface to prove request construction, parsing, rendering, branching, filtering, and cursor termination—not auth, tenancy, idempotency, freshness, or upstream integration.

Run the sandbox quickstart Compare normative examples