Documentation
Agent ToolsPOST

Agent Whois

WHOIS lookup for a domain. Returns registrar, registration and expiry dates, name servers, domain status flags, and registrant organisation (when available). All date strings are returned as-is from the WHOIS server — formats vary by registrar. `null` fields mean the WHOIS record did not include that data. `error` is non-null when the WHOIS server was unreachable or timed out. Results are cached for 24 hours. Example request: {"domain": "acme.com"} Signals agents should act on: - expires_at → check if domain is about to expire - registrant_org → verify sender organisation matches claimed identity - error != null → WHOIS unavailable, treat domain as unverified - status list → "clientHold" or "serverHold" means domain is suspended Use POST /v1/agent/tools/whois when you need this capability from your application or backend. It accepts a JSON request body. There are no query parameters for this operation.

Endpoint

Use this full URL directly in server-side integrations, scripts, or internal tooling.

POST request
https://api.dropfakes.com/api/v1/agent/tools/whois
Full endpoint URL
POST https://api.dropfakes.com/api/v1/agent/tools/whois

Authorization

This section explains how this endpoint should be called in the current API version.

No authorization required
This endpoint is documented as public in this version of the API reference. No bearer token is required.
Authorization
Authorization: dk_live_*****

Code examples

Start with curl, then use the language sample that matches your backend.

curl
curl -X POST "https://api.dropfakes.com/api/v1/agent/tools/whois" \
  -H "Content-Type: application/json" \
  -d '{
  "domain": "example.com"
}'

Parameters

Query string parameters and request body fields are listed together for faster scanning.

NameLocationTypeRequiredDescriptionDefault
domainbodystringYesBody field for `domain`.-

Success response

The primary success status for this operation is 200.

Status 200
Successful Response
200 application/json
{
  "domain": "example.com",
  "registrar": "string",
  "registered_at": "string",
  "expires_at": "string",
  "updated_at": "2026-03-21",
  "name_servers": [],
  "status": [],
  "registrant_org": "string",
  "cached": false,
  "error": "string"
}

Error response

Use this example to handle validation and request errors safely on the client or backend.

Status 422
Validation Error
422 application/json
{
  "detail": [
    {
      "loc": [
        "string"
      ],
      "msg": "string",
      "type": "string"
    }
  ]
}