How the platform actually behaves.
Payment, provisioning, networking, recovery, and operations—answered from the implemented contracts.
- + Base
eip155:8453 - + Polygon
eip155:137 - + Arbitrum
eip155:42161 - + Native: XMR
Can autonomous agents purchase Hyrule Cloud services directly?
Yes. Agents can discover the x402 manifest at https://cloud.hyrule.host/.well-known/x402.json, call a resource, satisfy the returned payment requirements, and retry with a Payment-Signature header. VM creation returns a public status URL and a save-once management URL. See the agent integration guide.
What payment methods do you accept?
USDC via x402 on Base, Polygon, Arbitrum. Native VM checkout rails currently enabled: XMR. The browser reads this list from the API rather than hardcoding it.
How fast is provisioning?
Typical VM builds complete in about 60 seconds. The homepage shows a sanity-checked live average, and each create response includes a public status URL that moves from payment_required to provisioning and then provisioned, failed, or rolled_back.
Why IPv6-first? What if a workload needs IPv4?
Every VM receives globally routed IPv6 inside 2a0c:b641:b51::/48. NAT64 and DNS64 translate outbound connections to IPv4 destinations. Inbound IPv4 to customer VMs is not available in v1.
Where can I see platform health?
The header status control and /status publish customer-impacting monitoring for API checkout, compute, network intelligence, domains and DNS, and network proxy. A VM also has its own lifecycle status URL.
How do accounts and password recovery work?
Accounts use a generated H<10 hex> handle. Recovery uses either the single-use recovery code shown at signup or a signature from an EVM wallet that previously paid on the account. Without either proof, the account cannot be recovered.
Do you require KYC?
No. Hyrule Cloud uses a no-KYC ordering model. One-shot orders can be placed without an account, and optional accounts use a generated handle rather than an identity profile.
What service data do you retain?
Hyrule Cloud stores the VM or service configuration, SSH public key where applicable, generated identifiers, lifecycle and payment state, and the minimum wallet metadata required to reconcile payment. The privacy page contains the complete inventory and retention policy.
Can Hyrule Cloud inspect what runs on my VM?
Customer VMs do not run a Hyrule monitoring agent. Network and host telemetry is used for reliability, capacity, and abuse response, but VM disk contents are not proactively inspected.
Where is the platform operated?
Hyrule Cloud is operated from the Netherlands. Current routing, peering, and infrastructure details are published by AS215932; our mission and operating policies live on the About & policy page.
How do I report abuse or request support?
Email support@hyrule.host. Use “Abuse report” in the subject for abuse cases and include the affected hostname, address or URL, evidence, timestamp with timezone, and urgency.
What if I overpay on a native crypto intent?
When native intent rails are enabled, an overpayment can still provision normally. A late payment may be accepted against a fresh rate quote within the published slippage policy; underpayments are held for manual review.