Clusters
Clusters is a multichain namespace and identity service that gives users a single universal name across blockchain ecosystems instead of a separate domain per chain. A Clusters name uses the format username/wallet (for example username/eth or username/sol) to bundle many wallets — EVM chains, Solana, and more — under one hierarchical, human-readable profile. The Clusters v1 REST API resolves an address to its cluster and wallet name and back, reads full cluster profiles, checks name availability, produces on-chain registration transaction data for EVM and Solana, registers community cluster names, and exposes a replayable historical event feed for permissionless indexing. Reads are public; wallet management and registration require a wallet-signature bearer token, and an optional API key raises rate limits. The protocol uses a hub-and-spoke model bridged with LayerZero v2 and replicates metadata to Arweave for data availability. Backed by Electric Capital.
Clusters publishes 6 APIs on the APIs.io network, including Authentication API, Clusters API, Communities API, and 3 more. Tagged areas include Company, Infrastructure, Identity, Naming, and Blockchain.
Clusters’ developer surface includes authentication, documentation, API reference, getting-started guide, signup flow, engineering blog, sandbox, and 24 more developer resources.
Kin Score
APIs 6
Individual APIs this provider publishes, each with its own machine-readable definition.
Clusters Authentication API
Wallet-signature authentication for write operations
Clusters Clusters API
Read and create clusters (profiles bundling wallets)
Clusters Communities API
Community cluster name availability and registration
Clusters Events API
Replayable historical event feed
Clusters Names API
Resolve addresses to cluster/wallet names and back
Clusters Registration API
Check availability and build registration transaction data
Arazzo Workflows 3
Multi-step API workflows described with the Arazzo specification.
_Index
ARAZZOCheck availability and build Clusters registration data
Check whether a name is available, then build the EVM registration transaction data to sign.
ARAZZOResolve a Clusters name to a wallet and profile
Bulk-resolve a cluster name to its address, then read the full cluster profile.
ARAZZOMCP Servers 1
Model Context Protocol servers that expose these APIs to AI agents.
clusters-mcp.yml
MCP SERVERSecurity Posture 3
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Agentic Access 1
Recommended x-agentic-access execution contracts for AI agents.
Resources
Get Started 4
Portal, sign-up, and the first successful call
Documentation 2
Reference material describing how the API behaves
Agent Surfaces 5
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 7
Pagination, idempotency, versioning, errors, and events
Scroll for all 7
Build 3
SDKs, sample code, and the tooling you integrate with
Access & Security 4
Authentication, authorization, and security posture
Operate 1
Status, limits, changes, and where to get help
Commercial 2
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