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.

🌐 Visit website 📡 Source on GitHub

20.6/100 emerging ▬ flat Agent 21/100 agent aware saas Full breakdown ↓
scored 2026-09-08 · rubric v0.20.0

1 APIs

Company Infrastructure IdentityNamingBlockchain Web3 Wallets Multi-Chain Resolver

Kin Score

Kin Score How this is scored →
scored 2026-09-08 · rubric v0.20.0

Composite quality — 20.6/100 · emerging

Contract Quality 0.0 / 19

Developer Ergonomics 8.5 / 15

Access Clarity 0.0 / 15

Operational Transparency 1.0 / 10

Contract Governance 0.4 / 9

Discoverability 5.7 / 8

Regulatory Posture 5.4 / 15

Create-or-Update Ergonomics 0.0 / 10

Agent readiness — 21/100 · agent aware

Machine-Readable Contract 18 / 18

Agentic Access Contract 10 / 10

Documented Reversibility 0 / 6

MCP Server 0 / 12

Machine-Readable Auth 10 / 10

Idempotency 0 / 9

Stable Error Semantics 8 / 8

Request/Response Examples 0 / 7

Rate-Limit Signaling 0 / 7

Typed Event Surface 0 / 6

Agent Skills 5 / 5

Well-Known Catalog 0 / 4

Consent & Bot Identity 0 / 3

A2A Agent Card 0 / 8

Dry-Run / Simulate Mode 0 / 4

Delegated User Identity 0 / 6

Protected Resource Metadata 0 / 5

Registration Without a Human 0 / 6

Agentic Commerce Well-Known Document 0 / 5

Regulatory Posture applies to this provider. Its tags matched the Payments regime, so Regulatory Posture carries 15 points of the composite. If this regime is wrong for your business, say so on your provider repo — the applicability map is public and we will correct it.

Create-or-Update Ergonomics applies to this provider. This API accepts writes, so it carries 10 points of the composite. It is scored from the published contracts themselves: whether a caller can create-or-update in one call, whether the write accepts a key the caller already holds, and whether the response says which branch ran. Without that, every write needs a search-and-branch in front of it, and the first time that check is skipped a duplicate record is created. Scored against the observed mean rather than raw — a provider at the catalog average is unchanged by this facet, not penalised by it.

The six quality facets above are damped to 75 points between them, because the conditional facet above carries the other 25. That is why each facet's contribution is shown against a damped maximum: raising a quality facet moves the composite by 75% of its nominal weight, not 100%. The full arithmetic is at apis.io/rating/.

Improve this rating by publishing the missing artifacts — every area above can be raised, and the full rubric is at apis.io/rating/. Every facet and dimension name above is a link: it opens that measurement's own page — what it means, the exact checks that feed it, how the whole catalog distributes on it, and the providers at the top of it. This rating is computed from github.com/api-evangelist/clusters: open an issue to ask a question, or submit a pull request to add artifacts. Submit an artifact on GitHub — free → Manage your own listing — the Influence plan, $499/mo →

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

Open Collections 7

Open, tool-agnostic API collections (OpenAPI-derived and Bruno).

API Collection

OPEN COLLECTION

Clusters Authentication API

OPEN COLLECTION

Authentication Clusters API

OPEN COLLECTION

Clusters Authentication Communities API

OPEN COLLECTION

Clusters Authentication Events API

OPEN COLLECTION

Clusters Authentication Names API

OPEN COLLECTION

Clusters Authentication Registration API

OPEN COLLECTION

Scroll for all 7

Arazzo Workflows 2

Multi-step API workflows described with the Arazzo specification.

Check availability and build Clusters registration data

Check whether a name is available, then build the EVM registration transaction data to sign.

ARAZZO

Resolve a Clusters name to a wallet and profile

Bulk-resolve a cluster name to its address, then read the full cluster profile.

ARAZZO

Security Posture 3

Authentication, domain security, vulnerability disclosure, and trust-center signals.

Clusters Authentication

apiKey/http · 2 schemes

SECURITY

Clusters Domain Security

TLSv1.3 · HSTS

SECURITY

Clusters Vulnerability Disclosure

disclosure policy published

SECURITY

Agentic Access 1

Recommended x-agentic-access execution contracts for AI agents.

Clusters Agentic Access

14 operations · 7 acting

AGENTIC

Resources

Get Started 4

Portal, sign-up, and the first successful call

DeveloperPortal

GettingStarted

SignUp

Sandbox

Documentation 2

Reference material describing how the API behaves

Documentation

Documentation

APIReference

APIReference

Agent Surfaces 5

MCP servers, agent skills, and machine-readable catalogs

AgenticAccess

AgenticAccess

LLMsTxt

LLMsTxt

WellKnown

WellKnown

X-MCPServerCandidate

X-MCPServerCandidate

AgentSkill

AgentSkill

Design & Contract 7

Pagination, idempotency, versioning, errors, and events

Conformance

ErrorCatalog

Lifecycle

Conventions

DataModel

Arazzo

Arazzo

Scroll for all 7

Build 3

SDKs, sample code, and the tooling you integrate with

GitHubOrganization

GitHubOrganization

SDKs

SDKs

Packages

Packages

Access & Security 4

Authentication, authorization, and security posture

VulnerabilityDisclosure

VulnerabilityDisclosure

Security

Security

DomainSecurity

DomainSecurity

Authentication

Authentication

Operate 1

Status, limits, changes, and where to get help

Deprecation

Deprecation

Commercial 2

Pricing, plans, and the legal terms of use

TermsOfService

TermsOfService

PrivacyPolicy

PrivacyPolicy

Company 2

The organization behind the API

Website

Website

Blog

Blog

Other 1

Properties that don't map to a standard resource type

Overlay

Overlay

Source (apis.yml)

aid: clusters
name: Clusters
description: 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.
url: https://raw.githubusercontent.com/api-evangelist/clusters/refs/heads/main/apis.yml
x-type: company
x-source: vc-portfolio
x-backed-by:
- electric-capital
x-tier: profiled
x-tier-reason: enriched-from-public-docs
deliveryModel:
  model: saas
  open_source: false
  commercial: true
  callable_host: true
  label: Hosted service · you call their endpoint
  confidence: high
  source:
  - openapi
  - pricing
  generated: '2026-08-28'
  method: derived
accessModel:
  pricing: unknown
  onboarding: unknown
  trial: false
  try_now: false
  public: false
  label: Unknown
  confidence: low
  source:
  - authentication
  - security
  - sandbox
  generated: '2026-09-03'
  method: derived
specificationVersion: '0.23'
created: '2026-07-17'
modified: '2026-07-18'
image: https://clusters.xyz/assets/images/apple/apple-touch-icon.png
tags:
- Company
- Infrastructure
- Identity
- Naming
- Blockchain
- Web3
- Wallets
- Multi-Chain
- Resolver
tags_raw:
- Company
- Infrastructure
- Identity
- Naming
- Blockchain
- Web3
- Wallet
- Multichain
- Resolver
apis:
- aid: clusters:clusters-authentication-api
  name: Clusters Authentication API
  description: Wallet-signature authentication for write operations
  humanURL: https://docs.clusters.xyz/getting-started/api/v1
  baseURL: https://api.clusters.xyz/v1
  tags:
  - Authentication
  properties:
  - type: OpenAPI
    url: openapi/clusters-authentication-api-openapi.yml
  - type: APIReference
    url: https://docs.clusters.xyz/getting-started/api/v1
- aid: clusters:clusters-clusters-api
  name: Clusters Clusters API
  description: Read and create clusters (profiles bundling wallets)
  humanURL: https://docs.clusters.xyz/getting-started/api/v1
  baseURL: https://api.clusters.xyz/v1
  tags:
  - Cluster
  tags_raw:
  - Clusters
  properties:
  - type: OpenAPI
    url: openapi/clusters-clusters-api-openapi.yml
  - type: APIReference
    url: https://docs.clusters.xyz/getting-started/api/v1
- aid: clusters:clusters-communities-api
  name: Clusters Communities API
  description: Community cluster name availability and registration
  humanURL: https://docs.clusters.xyz/getting-started/api/v1
  baseURL: https://api.clusters.xyz/v1
  tags:
  - Communities
  properties:
  - type: OpenAPI
    url: openapi/clusters-communities-api-openapi.yml
  - type: APIReference
    url: https://docs.clusters.xyz/getting-started/api/v1
- aid: clusters:clusters-events-api
  name: Clusters Events API
  description: Replayable historical event feed
  humanURL: https://docs.clusters.xyz/getting-started/api/v1
  baseURL: https://api.clusters.xyz/v1
  tags:
  - Event
  tags_raw:
  - Events
  properties:
  - type: OpenAPI
    url: openapi/clusters-events-api-openapi.yml
  - type: APIReference
    url: https://docs.clusters.xyz/getting-started/api/v1
- aid: clusters:clusters-names-api
  name: Clusters Names API
  description: Resolve addresses to cluster/wallet names and back
  humanURL: https://docs.clusters.xyz/getting-started/api/v1
  baseURL: https://api.clusters.xyz/v1
  tags:
  - Name
  tags_raw:
  - Names
  properties:
  - type: OpenAPI
    url: openapi/clusters-names-api-openapi.yml
  - type: APIReference
    url: https://docs.clusters.xyz/getting-started/api/v1
- aid: clusters:clusters-registration-api
  name: Clusters Registration API
  description: Check availability and build registration transaction data
  humanURL: https://docs.clusters.xyz/getting-started/api/v1
  baseURL: https://api.clusters.xyz/v1
  tags:
  - Registration
  properties:
  - type: OpenAPI
    url: openapi/clusters-registration-api-openapi.yml
  - type: APIReference
    url: https://docs.clusters.xyz/getting-started/api/v1
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com
- FN: APIs.json
  email: info@apis.io
common:
- type: VulnerabilityDisclosure
  url: security/clusters-vulnerability-disclosure.yml
- type: Security
  url: https://clusters.xyz/vulnerability-disclosure
- type: DomainSecurity
  url: security/clusters-domain-security.yml
- type: AgenticAccess
  url: agentic-access/clusters-agentic-access.yml
- type: Authentication
  url: authentication/clusters-authentication.yml
- type: Website
  url: https://clusters.xyz/
- type: DeveloperPortal
  url: https://clusters.xyz/developer
- type: Documentation
  url: https://docs.clusters.xyz/
- type: APIReference
  url: https://docs.clusters.xyz/getting-started/api/v1
- type: GettingStarted
  url: https://docs.clusters.xyz/getting-started/javascript
- type: SignUp
  url: https://clusters.xyz/developer
- type: GitHubOrganization
  url: https://github.com/clustersxyz
- type: Blog
  url: https://clusters.xyz/blog
- type: TermsOfService
  url: https://clusters.xyz/terms
- type: PrivacyPolicy
  url: https://clusters.xyz/privacy
- type: SDKs
  url: packages/clusters-packages.yml
- type: Packages
  url: packages/clusters-packages.yml
- type: LLMsTxt
  url: llms/clusters-llms.txt
- type: WellKnown
  url: well-known/clusters-well-known.yml
- type: X-MCPServerCandidate
  url: mcp/clusters-mcp.yml
  note: 'Renamed from MCPServer 2026-09-03 (roadmap#247): the manifest self-describes as status: candidate — a tool list derived
    from the published API contracts, not an existing server. The scorer already read the manifest and reported mcp_server
    correctly; the MCPServer type was crediting the artifact-type surfaces with a server that does not exist.'
- type: Overlay
  url: overlays/clusters-v1-overlay.yaml
- type: Conformance
  url: conformance/clusters-conformance.yml
- type: ErrorCatalog
  url: errors/clusters-problem-types.yml
- type: Lifecycle
  url: lifecycle/clusters-lifecycle.yml
- type: Deprecation
  url: lifecycle/clusters-lifecycle.yml
- type: Conventions
  url: conventions/clusters-conventions.yml
- type: DataModel
  url: data-model/clusters-data-model.yml
- type: Sandbox
  url: sandbox/clusters-sandbox.yml
- type: AgentSkill
  url: skills/_index.yml
- type: Arazzo
  name: Resolve a Clusters name to a wallet and profile
  url: arazzo/clusters-resolve-name.yml
- type: Arazzo
  name: Check availability and build Clusters registration data
  url: arazzo/clusters-register-name.yml
x-enrichment:
  date: '2026-07-19'
  status: backfilled
  pass: local-v1
  note: backfilled from .gitignore signal + verified work evidence

Work with this as data

Every provider here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for providers

9 MCP tools reach this

find_providersBrowse and filter every provider in the catalog.
get_provider_artifactsEvery artifact this provider publishes, grouped by type.
get_provider_operationsEvery operation across all of their OpenAPIs — one call instead of parsing every spec.
get_provider_toolsEvery MCP tool they ship, with the operation each wraps.
get_provider_evidenceHow each part of their score was established. Free — the basis for a claim should not sit behind it.
get_provider_ratingPRO — composite, band, trend and facet scores.
apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
resolveTurn a domain, URL or GitHub org into the provider it belongs to.
find_cohortsEvery scored population of providers in the catalog.

All 92 tools →

Call it yourself

curl for this page

This provider

curl "https://apis.io/api/v1/providers/clusters"

All providers

curl "https://apis.io/api/v1/providers?limit=25"

Every operation they expose

curl "https://apis.io/api/v1/providers/clusters/operations?limit=25"

How their score was established

curl "https://apis.io/api/v1/providers/clusters/evidence"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.