Transport-agnostic
Prepare a call and dispatch it with your own HTTP layer, or configure a sender once and let the client do it.
Developers
Ship trust in a few lines.
One official SDK: the typed Python client VerifAIerClient. Eleven services over the runtime that already exists, and the twelve open governance operations derived from the contract that defines them.
# Send it, with a sender you supply from vailidator.sdk import VerifAIerClient client = VerifAIerClient.for_user("you") gov = client.governance.with_base_url("http://localhost:8000").with_sender(send) answer = gov.assess_trust({"evidence": envelope}) print(answer.payload["trust_level"])
# Or build it and send it yourself call = client.governance.prepare("assessTrust", {"evidence": envelope}) call.method # POST call.url # /api/v1/trust/assess call.body # the JSON to send
What kind of client this is
Three properties, and none of them is a second engine.
Derived from the contract
The twelve open operations are read out of the allowlist that makes an endpoint public, so the client cannot drift from it.
No lock-in
Typed models over the runtime that already exists. No second engine, no new auth, no hidden network and no telemetry.
The OEM SDK Foundation is retired. The standalone packages under
sdk/python (verifaier_sdk) and sdk/typescript (@verifaier/sdk) are retired (WP-10I) and superseded by VerifAIerClient.governance. They were never published, they still build requests exactly as before because partners may have vendored them, and they are not where new work goes. There is no current TypeScript client; the supported TypeScript path is fetch against the open API, which needs no credential. See the SDK reference.One evidence layer
Related platform components
Not separate tools keeping separate records. Each of these derives from the same attested evidence, so you can adopt them in any order.
Integrate in an afternoon.
Grab the SDK and ship your first attested assessment.