API documentation

What H-Cert does

An owner connects an EVM wallet and names a principal: a subject identity, a claim (operated-by or trusted), scopes, and a private label. The owner signs the delegation as EIP-712. H-Cert verifies the signature against the owner, then anchors a commitment (a hash of each identity with a per-record salt, never the raw identifier) on Hedera Consensus Service. The public record proves a vouch is owner-signed and intact without revealing who is named. An owner reads their resolved roster through an authenticated view, and can hand an auditor the identity and salt to reproduce any commitment keylessly.

Alongside each vouch, H-Cert joins a behavior-backed standing for the subject, computed from how it has actually acted across the H-Series. Risk events emitted by H-Grant, H-Gate, H-Relay, H-Scope, and H-Agent (carried on the shared audit topic and read through H-Index), together with H-Seal receipts and H-Scope posture, fold into a decayed risk load that lowers the standing tier while risk is recent and recovers as it decays. It is fail-soft and can only cap a subject down, at most to suspended, never revoke. The standing is advisory: a consumer such as H-Grant or H-Pact resolves your directory and gates on the standing tier at its own trust boundary; H-Cert itself never blocks a call.

The Agent Track Record card is the free, public read of this standing: a subject's current tier and the behavior behind it. It is a record of observed behavior, not a score, rating, or verdict.

Returns the service configuration: the ruleset version, the standing topic ID, the read mode, the operator key metadata, and whether anchoring is enabled.

{
  "rulesetVersion": "standing-v1.0.0",
  "standingTopicId": "0.0.10601816",
  "readMode": "http",
  "operatorKeyId": "h-cert-op-1",
  "operatorPublicKey": "MCowBQYDK2Vw...",
  "operatorKeyStable": true,
  "anchoring": true,
  "store": "postgres"
}