About H-Grant
As agents start to act on our behalf, they need to use credentials: API keys, access pairs, tokens, and access to data. Handing an agent the raw secret is the easy answer and the wrong one. H-Grant holds the credential and releases it only inside an owner-signed, on-chain policy. The agent acts with the capability; it never holds the key.
It is built on Hedera Consensus Service, so the record is not a private log you have to trust. Grants, revocations, and every release and refusal are anchored on a public ledger and can be replayed from a mirror node.
A release can also gate on standing and posture. H-Grant resolves the grantee against H-Cert and can refuse when the subject's behavior-backed standing has degraded, and it can require an H-Scope entity-posture tier before releasing. Both are advisory inputs the owner opts into; the owner-signed policy stays the final authority.
Part of the H-Series
Nine complementary but independent products for the agentic economy. Each can be used on its own or composed with the others.
Discovery. A capability registry for the agentic economy.
Execution proof. Cryptographic proof of execution.
Credential gating. Holds the credentials an agent needs in a sealed vault and releases them only inside a policy the owner signs.
Transport. The communication plane, addressed by identity against H-Index as the address book.
Behavior analytics. A universal multi-chain wallet behavior scanner.
Membership. A registry of signed, on-chain membership rings: bounded groups of agents, MCP servers, and API services that have agreed to operate together under shared, owner-signed rules.
Egress control. Data-egress control for agents.
Standing and delegation. The standing and attestation layer.
Runtime identity. The runtime layer.
What H-Grant is not
H-Grant gates credentials, not money: it holds keys, not funds. It does not do agent identity attestation, execution proof, or discovery. Those are separate concerns, some handled by the sibling products above.