H-Series: Infrastructure for the agentic economy

Where is the agent or service, and what can it do?

A capability registry for the agentic economy. Publishers register MCP servers and API endpoints, gated by a one-time micropayment, with an optional signed snapshot of the server's tool manifest. Discovery is free, served from a local index with semantic search.

Standalone: A working, paid registry agents query directly. It is also the shared address book every other product resolves identities against, and it serves the Agent Track Record risk feed at /risk-events. Its safety scanner runs a signed, weekly-curated ruleset published on chain (HCS topic 0.0.10534406), so the detection logic is auditable, not a black box.

Can you prove what was asked, and what was done?

Cryptographic proof of execution. A receipt anchors hashes of the request and response with identities and timestamps; payloads stay off-chain. The symmetric request envelope (the notary) anchors the ask before the call, so envelope and receipt bracket a full interaction.

Standalone: Any MCP service, API, or agent-to-agent call can anchor receipts without being listed anywhere. An SDK lets a provider sign its half of a receipt.

What is this agent allowed to do with real accounts?

Holds the credentials an agent needs in a sealed vault and releases them only inside a policy the owner signs. The agent never sees the raw secret; a broker checks the active grant, executes the call, and anchors every release or refusal. A signed revocation is the freeze button.

Standalone: Gates credentials for any agent against any upstream API. The corporate-card model for software agents. A grant can gate on H-Cert standing and H-Scope posture, holding a release when a grantee's Agent Track Record has degraded.

How does the message actually reach the agent?

The communication plane, addressed by identity against H-Index as the address book. Three modes are live: Inbox (point-to-point store-and-forward), Broadcast (one-to-many liveness heartbeat), and Relay (fetch-through context proxy).

Standalone: An agent messaging and liveness service addressed by identity. Optionally calls H-Seal to stamp a delivery with proof.

How does this wallet behave, and what kind of actor runs it?

A universal multi-chain wallet behavior scanner. It turns any on-chain address into deterministic behavioral signals, an entity-posture score, and an advisory narrative (a deterministic gloss, with an optional gated LLM summary), from one engine across five chains. Descriptive context, not a risk or compliance verdict.

Standalone: Scan any address on its own: free in the showroom, $0.10 per scan on the agent x402 API. Other H-Series products can consume its posture signal as an input, and it emits an abuse-flag risk signal into the Agent Track Record. Its calibration corpus of on-chain-verified wallets is anchored to a Hedera Consensus Service topic as immutable, versioned snapshots, so the labeling is tamper-evident and reconstructible from a public mirror replay.

Which agents, MCP servers, and API services have agreed to operate together, and who is in the ring?

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. A twin of H-Index, but a registry of memberships rather than capabilities, with membership recorded on chain as salted commitments and identities readable only through an authenticated query.

Standalone: Create and govern a ring on its own: $5 to create, admit and evict free. The other H-Series products can honor a ring (reachability, allowlist, ring-scoped visibility) through opt-in seams.

What is this agent allowed to send out, and can you prove what left?

Data-egress control for agents. Outbound payloads pass through an owner-signed policy that decides what an agent may send to which destination; blocked, redacted, and allowed sends are recorded. Control what your agents send, and prove it.

Standalone: Gate the egress of any agent against any destination on its own. Every decision can anchor to H-Seal for proof of what left and what was held back, and a blocked send emits an egress-denied risk signal into the Agent Track Record.

Whose agent is this, and can it be trusted to act?

The standing and attestation layer. An owner builds a named, owner-signed directory of their agents and counterparties (anchored as salted commitments, never the raw identity), and the service issues a behavior-driven standing that rises with clean, proven activity and degrades when risk shows up across the ecosystem. It reads the risk events the other products emit, folds them into a decayed risk load, and caps the tier down while risk is present; the tier recovers as risk decays.

Standalone: Name and attest your principals on its own; the other products consume the delegation and standing at their trust decision points. The public read is Agent Track Record: a free description of how an entity has actually behaved. Advisory and fail-soft, it caps a tier down at most to suspended, never revoked.

How does an agent hold an identity and spend under a limit?

The runtime layer. An owner logs in and H-Agent mints the agent an MPC-held wallet, then hands back a connection string to paste into Claude. Provisioning mints identity only; a USDC spend cap is materialized from an owner-signed H-Grant grant and enforced on chain by the Spend Permission contract. The owner keeps the funds; the agent can check who it is, see its remaining cap, and pay, all within the limit.

Standalone: Give an agent an identity and a spend cap and connect it to Claude on its own; it can publish an operated-by claim to H-Cert and pay for an H-Scope scan within the cap. A real-time detector emits a risk signal when the agent trips a control, and the agent self-gates on its own Agent Track Record. It can also issue a Know Your Agent (KYA) token, the open KYAPay standard, so a merchant can admit the agent at checkout instead of blocking it as a bot, privacy-first and with the spend cap read live on chain. H-Agent holds no key and no money. Runs on Base mainnet.