Web3 Name API
The public Hyndle Web3 Name API is being designed as a stable HTTP interface for wallets, applications, exchanges, and protocol infrastructure. It is not publicly available yet, and no internal application endpoint should be treated as a supported integration surface.
The initial release will focus on the two operations most integrations need: resolving a Hyndle name to network-specific address records and resolving an address back to an eligible primary Hyndle name. Availability, ownership lifecycle, metadata, and supported-record discovery are planned as complementary resources.
Planned capabilities
- forward resolution from a Hyndle name to supported address records
- reverse lookup from a wallet address to an eligible primary name
- name availability and lifecycle lookup
- supported network and record-type discovery
- deterministic name identity lookup
Publication requirements
Before public access is announced, this page will document:
- production base URL and versioning
- authentication requirements
- request and response schemas
- error model
- rate limits and caching
- confirmation and consistency guarantees
- deprecation and compatibility policy
The register application's internal endpoints are documented separately and must not be treated as this public API. See Application API.
Integration status
API credentials, production origins, endpoint examples, and client snippets will be published only after the public schema, rate limits, cache behavior, and compatibility policy have completed security review. Until that announcement, integrations should use the verified contracts and resolver interfaces documented by Hyndle rather than guessing endpoint URLs.
When the API becomes available, this page will be the authoritative location for its versioned contract and migration notices.