API Reference

Complete reference documentation for the RobotDomainSearch API.

Base URL

https://api.robotdomainsearch.com

Endpoints

Endpoint Method Description Price
/v1/check GET Check domain availability (supports bulk TLD and category checks) Free
/v1/whois GET WHOIS / RDAP domain lookup Free
/v1/dns/{domain} GET DNS record lookup (A, AAAA, MX, NS, TXT, SOA, DNSSEC) Free
/v1/intel GET Domain intelligence (parked detection, screenshot) $0.05
/v1/auctions GET Browse live domain auctions Free
/v1/tlds GET List supported TLDs (511 TLDs across 15 categories) Free
/v1/register GET Get registration links Free
/v1/aftermarket/{domain} GET Check aftermarket listings Free
/v1/valuation/{domain} GET Estimate domain market value $0.02–$0.08
/v1/name-search-presence GET Check search engine presence for a name or brand $0.02
/health GET API health check Free

Trademark API

Search the USPTO trademark database. ~14M records with full-text, phonetic, and fuzzy matching.

Endpoint Method Description
/v1/trademark/search GET Search trademarks by mark text
/v1/trademark/search/description GET Search by goods/services description
/v1/trademark/search/owner GET Search by owner name
/v1/trademark/search/expiring GET Find expiring trademarks
/v1/trademark/search/status GET Trademark index status

ENS API

The ENS (Ethereum Name Service) endpoints provide .eth name availability and metadata lookups. ENS is proxied through the main API.

Base URL:

https://api.robotdomainsearch.com
Endpoint Method Description
/v1/ens/check GET Check ENS name availability + pricing
/v1/ens/metadata GET Get ENS metadata (address, avatar, social links)
/v1/ens/health GET ENS service health check

Request Format

All endpoints accept query parameters:

curl "https://api.robotdomainsearch.com/v1/check?name=example&tld=com"

Response Format

All responses are JSON. Each endpoint returns a different structure — see the individual endpoint docs for details.

Rate Limits

Rate limiting is applied to all requests. See Rate Limits for details.

Payments

Paid endpoints accept micropayments via two protocols — no API key required:

See Payments documentation for integration guides.

Errors

All errors return a consistent format:

{
  "error": "invalid_domain",
  "message": "The domain format is invalid",
  "code": 400
}

See Error Codes for the complete list.

SDKs & Tools

  • MCP Server: /mcp/ — For AI agent integration
  • OpenAPI Spec: /openapi.yaml — Full API specification
  • llms.txt: /llms.txt — Machine-readable overview