Integrate DNSUSD alias resolution into your application
To use the DNSUSD API, you'll need an API key. Create one from the API Keys page.
Include your API key in the Authorization
header as a Bearer token.
All API requests must include your API key in the Authorization header:
Authorization: Bearer dnsusd_live_...
/api/v1/resolve
Resolve a single alias to cryptocurrency addresses.
alias
(required) - The alias to resolve (e.g., example.com, user.eth)curl -X GET "https://dnsusd.app/api/v1/resolve?alias=example.com" \ -H "Authorization: Bearer YOUR_API_KEY"
{ "success": true, "data": { "alias": "example.com", "results": [ { "chain": "ETH", "address": "0x1234...", "source": "dns", "confidence": 0.95 } ], "resolved_at": "2025-01-14T12:00:00Z", "response_time_ms": 245 } }
/api/v1/resolve/batch
Resolve multiple aliases in a single request (max 100).
{ "aliases": ["example.com", "user.eth", "domain.crypto"] }
{ "success": true, "data": { "total": 3, "results": [ { "alias": "example.com", "success": true, "results": [...] }, ... ], "resolved_at": "2025-01-14T12:00:00Z", "response_time_ms": 512 } }
/api/v1/aliases/:alias/trust
Get trust score and verification status for an alias.
{ "success": true, "data": { "alias": "example.com", "trust_score": 85, "trust_level": "high", "verification_status": "verified", "last_verified_at": "2025-01-14T10:00:00Z", "response_time_ms": 123 } }
Rate limits vary by tier:
Rate limit information is included in response headers: X-RateLimit-Limit
, X-RateLimit-Remaining
, X-RateLimit-Reset
400
- Bad Request (missing or invalid parameters)401
- Unauthorized (invalid or missing API key)404
- Not Found (alias not found)429
- Too Many Requests (rate limit exceeded)500
- Internal Server Error