SDK
One official client, VerifAIerClient, in Python. The standalone Python and TypeScript OEM packages are retired.
Developers
Twelve endpoints. One trust surface.
The VerifAIer API is a consistent, production surface for evidence, intelligence, identity and distribution, the same endpoints the dashboard and SDKs use.
Reference
Everything, in one place.
POST/api/v1/audit/conversation
POST/api/v1/compliance/assess
POST/api/v1/risk/assess
POST/api/v1/quality/assess
POST/api/v1/trust/assess
POST/api/v1/passport/issue
POST/api/v1/reputation/assess
POST/api/v1/registry/observe
GET/api/v1/registry/agents
GET/api/v1/registry/agents/{id}
GET/api/v1/control-center/overview
POST/api/v1/signals/export
Consistent by design
Predictable requests, predictable proofs.
- Deterministic responses, same inputs, same IDs
- Additive envelopes you can persist and replay
- No secrets or prompts in responses
POST /api/v1/trust/assess Content-Type: application/json { "evidence": { "envelope_id": "ev_..." } }
One call, end to end
Request, evidence, response.
A real captured call to the audit endpoint. The envelope is created as part of answering the request, so evidence is not a second step you have to remember.
- RequestPOST /api/v1/audit/conversation{"input": "Summarize the key findings from the quarterly compliance re…
- Evidenceenvelope created
ev_b1d655f8935b407b91606c800423c9bb - Receiptemitted alongside the envelopeaudit_ai_response
- ResponseHTTP 200schema 1.0
The service reported version 1.4.2 when this was captured. The identifier above belongs to this API call and is deliberately not the same operation as the trace on the evidence engine page.
Captured output: api-audit.json · api-health.json
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.