HashKey Cloud (HashQuark)
HashKey Cloud, formerly HashQuark, is a Hong Kong-based blockchain infrastructure and Web3 staking provider (part of HashKey Group) that runs enterprise-grade validator nodes across 50+ mainstream proof-of-stake public chains including Ethereum, Cosmos, Solana, Polkadot, Avalanche, Sui and BNB Chain. It exposes a developer platform for institutional staking: a Staking API to onboard users, generate deposits, assign and exit validators and drive pooled staking; a Data API to track node status and daily/monthly/quarterly/ annual reward data; plus a dashboard, a Babylon BTC staking flow and a first-party Go SDK. Requests are authenticated with a custom Quark-Keccak256-ECDSA request-signing scheme keyed to an Ethereum keypair. Originally added to the API Evangelist network as a portfolio-lead stub (surfaced via Qiming), now enriched from HashKey Cloud's public developer surface.
More than an index entry, but the surface is still mostly links rather than artifacts — the cohort most likely to move a full band from modest, well-targeted work.
API Evangelist profiles HashKey Cloud (HashQuark) the way a machine reads it — 4 machine-readable artifacts across 2 APIs, pulled from the provider's own public surface and indexed so a developer, an analyst, or an AI agent can evaluate it against every other provider on the network.
Every provider in the network is reduced to the same set of machine-readable artifacts — OpenAPI contracts, event specifications, GraphQL schemas, runnable collections, pricing and rate-limit signals, security posture, OAuth scopes, and the agent surfaces (MCP servers and skills) that let software drive the API on its own. We profile them because the interface is the part of a company you can actually inspect: it is a truer signal of what a provider does than any marketing page. From those artifacts we compute the Kin Score — HashKey Cloud (HashQuark) scores 22.9/100 (emerging), with a separate agent-readiness read of 10/100 (human only). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.
Kin Score
This is the API Evangelist rating — a single, repeatable read computed from the artifacts on this page. Green fill is points earned; the red track is points possible, so every bar shows earned-versus-possible at a glance.
Kin Score
How this is scored →scored 2026-07-27 · rubric v0.5
How we profile HashKey Cloud (HashQuark)
Each block below is one kind of artifact we hold for HashKey Cloud (HashQuark). For each we say what it is and why it earns a place in the profile, then list every one we've indexed — capped at two rows, scroll within the panel for the rest.
APIs 2
Each API is captured as its own OpenAPI definition — every operation, parameter, and response. This is the single most useful machine-readable description of what an API does, and it's what lets us score, lint, mock, and generate against it without asking the provider for anything.
Individual APIs this provider publishes, each with its own machine-readable definition.
HashKey Cloud Staking API
Institutional staking API to onboard broker users, generate and track deposits, assign/exit validators, drive pooled staking and Babylon BTC staking across supported proof-of-st...
HashKey Cloud Data API
Reporting API for node status and staking reward data (daily, monthly, quarterly and annual rewards) for integrated staking users. Shares the Quark-Keccak256-ECDSA authenticatio...
Security Posture 2
Authentication, domain security, vulnerability disclosure, and trust-center signals — the evidence that a provider takes security seriously enough to document it. We profile it because you can't govern what you can't see.
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Resources
Every other property we hold for HashKey Cloud (HashQuark) — documentation, portals, status pages, policies, and corporate surface — grouped by the job it does, following the integrator's arc from getting started to running in production.
Get Started 2
Portal, sign-up, and the first successful call
Documentation 2
Reference material describing how the API behaves
Agent Surfaces 1
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 2
Pagination, idempotency, versioning, errors, and events
Build 3
SDKs, sample code, and the tooling you integrate with
Access & Security 2
Authentication, authorization, and security posture
Commercial 1
Pricing, plans, and the legal terms of use
Company 2
The organization behind the API
Other 1
Properties that don't map to a standard resource type
← All providers · Data indexed from github.com/api-evangelist/hashquark · machine-readable index on apis.io