About H-Agent
H-Agent is the runtime identity product in the H-Series, a family of Hedera-native infrastructure tools built by XR Utilities. It answers a single question: how does an agent hold an identity and spend under a limit? An owner logs in, sets a USDC spending cap, and H-Agent mints the agent an MPC-held wallet under an owner-signed, on-chain Spend Permission, then hands back a connection string to paste into Claude.
The owner keeps the funds and the cap is enforced on chain, not by us behaving well. The agent can check who it is, see its remaining cap, and pay, all within the limit. H-Agent holds no key and takes no custody: the agent's key lives in a Trusted Execution Environment (Coinbase CDP), and an over-cap transaction reverts on chain. Used on its own, an agent can publish an operated-by claim to H-Cert and pay for an H-Scope scan within the cap. Runs on Base mainnet.
H-Agent also runs a real-time risk detector over each action and emits a risk signal onto the shared H-Series audit topic, where it feeds the agent's H-Cert standing. Before it spends, the agent self-gates on that standing: when its own behavior-backed tier has degraded, it holds off rather than acting. This is advisory and fail-soft; the on-chain cap remains the hard limit.
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.
Use cases
Autonomous agent spend
Give an agent an identity it holds and a cap you sign, then connect it to Claude so it can pay for tools and services without ever exceeding your limit.
Capped merchant purchases
An agent buys from an x402 merchant within the owner-signed cap; the transaction reverts on chain if it would spend past the limit.
Non-custodial key holding
The agent's key is held in a secure enclave by Coinbase CDP. H-Agent has no raw key, so no operator ever moves the owner's funds.
Admitted at checkout, not blocked as a bot
H-Agent issues a Know Your Agent (KYA) token, the open KYAPay standard, that proves the agent is bound to an accountable person and capped, so a merchant can let it through checkout. Privacy-first: it shares no personal data unless you consent.
Composed with the H-Series
An H-Agent identity can publish an operated-by claim to H-Cert and pay for an H-Scope scan, all inside the same cap.