DomainCrust developer resources

DomainCrust API Documentation

Use the DomainCrust API when an application or agent needs structured domain sales data instead of a human-oriented page. The API provides searchable transactions, domain history, market statistics, TLD performance, marketplace statistics, and top-sale summaries. The complete request and response contract is available in the OpenAPI specification.

OpenAPI specification

Download the machine-readable JSON or YAML contract for every documented DomainCrust API endpoint.

Open openapi.json →

Agent instructions

Read the short machine-readable guide for choosing DomainCrust resources and calling the API.

Open llms.txt →

API basics

Base URL: https://domaincrust.com/api/v1
Read operations: Sales search, domain history, market statistics, TLD statistics, platform statistics, and top sales are documented as GET endpoints.
Authentication: Public read requests do not require a key. Write operations require an API key in the X-API-Key header and the permission described by the OpenAPI document.
Response format: Responses use JSON with a success flag, a data object for successful results, and structured error details when a request fails.
Rate limits: Responses expose RateLimit-Limit, RateLimit-Remaining, and RateLimit-Reset in seconds. A 429 response includes Retry-After. Read the versioning and deprecation policy before integrating.

Example request

An agent can search the sales dataset by sending a normal HTTPS request with query parameters. Use the OpenAPI file for the complete filter list and schema definitions.

curl "https://domaincrust.com/api/v1/sales/search?domain=crypto&limit=20"

For support, API access questions, or integration feedback, contact api@domaincrust.com. See the DomainCrust contact page for the public support context.

DomainCrust developer tooling

For scripted workflows, use the official DomainCrust CLI and its npm package page. The package source is distributed with the same endpoint names as this API documentation. Agents can start from DomainCrust llms.txt, read the API versioning policy, and choose the JSON OpenAPI contract when they need typed function-calling definitions.