Trust
Package trust is your trust centre: the controls you publish, the coverage they compute to, the documents a reviewer asks for, and who you send data to.
Package trust is your trust centre: the controls you publish, the coverage they compute to, the documents a reviewer asks for, and who you send data to.
| Base URL | https://api.hanzo.ai |
| Operations | 17 |
| Auth | Authorization: Bearer $HANZO_API_KEY |
Specification
Specification pending — no HIP in hanzoai/hips declares capability: trust yet. What this capability serves is below, from the API document; what it is — the store it owns, how it meters, what it publishes — is written as a HIP under HIP-0139.
Four surfaces
| Surface | Reaches this capability as | Coverage |
|---|---|---|
| REST | trust at its own prefix | 17 operations |
| CLI | — | no command reaches it yet — use HTTP or an SDK |
| SDK | — | no published client declares one yet — regenerating the clients is what adds them |
| MCP | — | no tool names it yet — use HTTP or an SDK |
Quickstart
export HANZO_API_KEY=sk-... # console.hanzo.ai → API keysThen the first call — a read that needs nothing but the key. GET /v1/trust, operation get_trust:
hanzo has no subcommand for this operation — the CLI serves only what cloud's live route table confirms. Use HTTP or an SDK.
import { Configuration, TrustApi } from 'hanzoai';
const api = new TrustApi(new Configuration({ accessToken: process.env.HANZO_API_KEY }));
const { data } = await api.getTrust();from hanzoai.cloud import ApiClient, Configuration
from hanzoai.cloud.api import TrustApi
client = ApiClient(Configuration(access_token=os.environ["HANZO_API_KEY"]))
result = TrustApi(client).get_trust()cfg := cloud.NewConfiguration()
cfg.AddDefaultHeader("Authorization", "Bearer "+os.Getenv("HANZO_API_KEY"))
client := cloud.NewAPIClient(cfg)
resp, _, err := client.TrustAPI.GetTrust(context.Background()).Execute()
if err != nil {
return err
}use hanzo_cloud::apis::{configuration::Configuration, trust_api};
let mut cfg = Configuration::new();
cfg.bearer_access_token = std::env::var("HANZO_API_KEY").ok();
let result = trust_api::get_trust(&cfg, Default::default()).await?;import ai.hanzo.cloud.ApiClient;
import ai.hanzo.cloud.api.TrustApi;
ApiClient client = new ApiClient();
client.setRequestInterceptor(b -> b.header("Authorization", "Bearer " + System.getenv("HANZO_API_KEY")));
var result = new TrustApi(client).getTrust();The method above is the one at the current release of the document. [email protected] (npm) and [email protected] (PyPI) were generated from an earlier release, where this operation carried a different id, so it spells the method differently — regenerating the clients is what makes the two agree. SDKs →
curl https://api.hanzo.ai/v1/trust \
-H "Authorization: Bearer $HANZO_API_KEY"The door declares no tool for trust — tools/list on https://api.hanzo.ai/v1/mcp names the products it does reach. Use HTTP or an SDK.
Answers 200 with object — ok.
Endpoints
| Endpoint | What it does |
|---|---|
PUT /v1/trust/{kind}/{id} | Writes one record into a section of YOUR organization's trust centre — profile, control, document, subprocessor, policy, faq, update or risk. |
DELETE /v1/trust/{kind}/{id} | Removes one record from a section of your organization's trust centre. |
GET /v1/trust/controls/{id} | Reads one control by id. |
GET /v1/trust/controls | Lists every control your organization publishes, with the counts. |
GET /v1/trust/coverage/{framework} | Reads one framework clause by clause: every clause the standard publishes, what covers it, and which controls stand behind it — so a coverage number… |
GET /v1/trust/coverage | Reads coverage: per framework, how many clauses have an automated control behind them, how many are partial, and how many have none — each carrying… |
GET /v1/trust/documents | Lists your organization's documents. |
GET /v1/trust/evidence | Reads the audit rows that stand behind one control, over a window. |
GET /v1/trust/faq | Lists your knowledge base — the questions a reviewer asks, answered once. |
GET /v1/trust/frameworks | Lists the frameworks coverage is computed against, and how many clauses each publishes. |
GET /v1/trust/policies | Lists your organization's published policies. |
GET /v1/trust/profile | Reads your organization's trust-centre profile — the name, tagline and summary a visitor sees, whether the centre is published, and where to send… |
GET /v1/trust/published/{org} | Reads a published trust centre — the whole thing in one answer: the organization's profile, its control inventory, coverage computed against each… |
GET /v1/trust/risk | Reads your risk profile — the label and value pairs describing what your organization handles and how. |
GET /v1/trust/subprocessors | Lists the third parties your organization sends data to, each naming what it is for. |
GET /v1/trust/updates | Lists your trust-centre updates, newest as you ordered them. |
GET /v1/trust | Reads YOUR organization's whole trust centre, including the addresses of your own gated documents. |
How is this guide?