Frequently asked questions

Answers that span the whole H-Series. For a single product, see its guide under Services. For the big picture, see Start here and Compose the ecosystem.

Is this live and production-ready?

The products are live on mainnet. H-Agent runs on Base; the rest anchor their records to Hedera. So the answer is yes, it is live, with honest qualifiers. First, it is early and founder-led, running on a single deployment with no high-availability failover, so treat it as production-live but pre-scale. Second, H-Grant credential custody runs the production nitro enclave LIVE (cutover 2026-07-26), so operator-zero-access is live, while H-Gate’s detection engine is live but its production enclave is not yet deployed, so H-Gate inspection is software-isolated today (see the data-safety question below).

Do I need crypto to use it?

For reading and browsing, no. Every showroom lets you look around and try the core action without paying. To authorize an action you need either a wallet or a Google sign-in, and any paid action settles in a stablecoin over x402.

If you would rather not deal with a wallet at all, H-Agent is built for that: sign in with Google, and H-Agent mints your agent an MPC-held key it holds in a secure enclave. You set a spend cap; you never manage a seed phrase.

What does it cost?

There is no subscription and no tier. You pay per paid action, in a stablecoin, over x402. The current schedule:

• H-Index (discovery): $10 one-time to register a listing, $5 a year to renew. Discovery, owner updates to your own listing, and revoke are free.
• H-Seal (proof): $0.05 per receipt anchored. Verifying a receipt is free and needs no account.
• H-Gate (egress): free in the showroom; $0.10 per inspection on the agent API.
• H-Scope (behavior): free in the showroom; $0.10 per scan on the agent API.
• H-Pact (membership): $5 one-time to create a ring; every governance action after that (admit, evict, policy update, renew, retire) is free.
• H-Agent (agent identity): when it makes a purchase for a third-party agent it adds a 3% fee on top of the merchant price. First-party estate apps are exempt. See the fee schedule.

How do agents pay?

Over x402. The agent presents a payment alongside its request, and the service being paid re-verifies the settlement on chain. The facilitator that relays the payment is never trusted; settlement is checked on chain, bound to the payer, and replay-guarded so the same payment cannot be reused. An agent using H-Agent pays within an owner-signed spend cap enforced on chain: an over-cap payment reverts and no funds move.

What chains and payments does it accept?

Stablecoins only at present:

• USDC on Hedera, Base, Solana, and Stellar.
• RLUSD on XRPL.

The volatile-asset rails (native HBAR, ETH, XRP, SOL, XLM) are built and retained behind a flag but are not currently offered. H-Agent’s on-chain spend cap is a USDC allowance on Base.

What is the difference between the showroom, the .ai, and the .com?

Same product, two front doors:

• The showroom is the product’s .com site, for a person: sign in, click through, watch it work.
• The backend is the product’s .ai API, for an agent or an integrator: signed requests, x402 payment, and where relevant an MCP tool surface at https://mcp.xr-utilities.ai/mcp.

They enforce the same guarantees; they differ only in audience. Each product guide in this Knowledge Base documents both.

Is my credential safe? Is my data safe?

Two custody surfaces, and it matters that you know the current state of each.

H-Grant credential custody runs the production nitro enclave, LIVE. A deposited credential is envelope-encrypted at rest and, in the production nitro mode (LIVE, cutover 2026-07-26), decrypted and used only inside an AWS Nitro enclave. AWS KMS releases the data key only to an enclave whose attestation matches a pinned measurement, so even someone with full access to the host cannot read the credential; that is operator-zero-access, live in production. The software kms mode is retained on the standby as an instant rollback. Either way, the agent presents a grant and gets back only the result; the secret never reaches the agent or the app process.

H-Gate egress inspection is live but not yet hardware-isolated. H-Gate’s detection engine is deterministic and enclave-safe by construction (no I/O, no clock, no network; only hashes, types, and spans leave it). Its production Nitro enclave is designed for but not yet deployed, so today it runs the engine in software. That means H-Gate inspection is software-isolated, not hardware-isolated. This is distinct from H-Grant, whose credential custody runs the nitro enclave live (operator-zero-access); the two are decoupled (H-Grant nitro-live, H-Gate software-isolated).

Across the suite, records anchor to public chains and are independently verifiable from a mirror node, so you do not have to trust the operator to trust the record.

Is it open source, and who runs it?

The H-Series is built and operated by XR Utilities. It is early and founder-led. The trust model does not depend on trusting the operator: authorizations are owner-signed over structured data, and records anchor to public chains where anyone can verify them from a mirror node without an account.

How do I get support?

Email contact@xr-utilities.com. A public support forum is planned but not yet open. Because the suite is founder-led and pre-scale, responses are direct but not instantaneous. For anything money- or safety-relevant, include the on-chain reference (a receipt id, a topic and sequence, a transaction hash) so the record can be checked directly.

Do I have to adopt all of it?

No. Every product runs standalone and is useful on its own. They share the same identity (CAIP-10), signing (TIP-712 / EIP-712 / Ed25519), and payment (x402) foundations, so adopting one makes the next familiar, but there is no all-or-nothing. Compose the ecosystem shows how they chain when you do want to use several together.