The Namedry API

Paginated feed of scored candidates — the same 'best' blend the site's daily table uses (name score + registry authority + brand read). This is the firehose most integrations pull.

curl "https://api.namedry.com/api/drops?min_score=95&available=true&limit=2"

{
  "domains": [
    {
      "domain": "deskkeep.com",
      "readable": "DeskKeep",
      "variations": ["DeskKeep"],
      "score": 100,
      "open_rank": 2.7,
      "available": true,
      "brand_score": 88,
      "brand_tags": ["two-word", "saas"],
      "brand_note": "Clean two-word compound, spells itself on hearing.",
      "list_date": "2026-07-17T00:00:00Z"
    }
  ],
  "total": 317,
  "page": 1,
  "limit": 2
}

Enrichment fields are null until fetched: open_rank (registry authority), available (RDAP), and the brand_* LLM signals. Under the best sort, un-enriched names sink to the bottom.

The full stored document for one domain — every signal we hold, including the Namecheap cross-check and the archived Wayback fields omitted from the list feed.

curl "https://api.namedry.com/api/domains/deskkeep.com"

{
  "_id": "deskkeep.com",
  "sld": "deskkeep",
  "readable": "DeskKeep",
  "variations": ["DeskKeep"],
  "score": 100,
  "source": "whoxy-2026-07-17",
  "list_date": "2026-07-17T00:00:00Z",
  "first_seen": "2026-07-17T07:02:11Z",
  "updated_at": "2026-07-17T07:40:03Z",
  "open_rank": 2.7,
  "available": true,
  "checked_at": "2026-07-17T07:31:55Z",
  "nc_available": true,
  "nc_premium": false,
  "nc_checked_at": "2026-07-17T07:33:10Z",
  "archive_first": "2012-04-02T00:00:00Z",
  "archive_last": "2019-11-18T00:00:00Z",
  "archive_months": 61,
  "archive_score": 48,
  "brand_score": 88,
  "brand_tags": ["two-word", "saas"],
  "brand_note": "Clean two-word compound, spells itself on hearing.",
  "judged_at": "2026-07-20T02:14:55Z"
}

Returns 404 {"error":"domain not found"}if we've never listed the name. Enrichment keys (open_rank, available, nc_*, archive_*, brand_*) are omitted entirely until their stage has run, rather than sent as null.

A LIVE RDAP availability lookup at the moment you ask — the truth check to run right before a user registers. Bare labels get .com appended automatically.

curl "https://api.namedry.com/api/check/deskkeep"

{
  "domain": "deskkeep.com",
  "available": true,
  "checked_at": "2026-07-17T09:14:22.481Z"
}

Hits RDAP on every call (no cache), so it's the slowest endpoint — reach for /api/drops?available=true for bulk. A failed upstream lookup returns 502; an invalid label, 400.

Run the brandability scorer on any name — no database, no registration state. This is the moat: the same scorer that ranks the daily drops, exposed for your own inputs.

curl "https://api.namedry.com/api/score/deskkeep"

{
  "score": 100,
  "readable": "DeskKeep",
  "variations": ["DeskKeep"]
}

readable is the best CamelCase wording; variations lists every max-coverage segmentation, best first. Pure function — safe to call at high volume from an agent.

Funnel counts for the most recent drop day — how many names were ingested, how many scored a perfect 100, and how many are available, plus how many clear a brand score of 80.

curl "https://api.namedry.com/api/stats"

{
  "latest_list_date": "2026-07-17T00:00:00Z",
  "total_ingested": 4192,
  "scored_100": 128,
  "available": 3106,
  "available_with_history": 214,
  "available_strong_brand": 372
}

An empty store returns all-zero counts and "latest_list_date": null. total_ingested and scored_100 are scoped to the latest list_date; available counts span the whole store.

How many available domains carry each brand tag — the taxonomy behind the browse-by-type pages. Form tags (one-word, two-word, multi-word, coined) are exclusive; modifier and market tags are optional.

curl "https://api.namedry.com/api/tags"

{
  "tags": [
    { "tag": "two-word", "count": 4831 },
    { "tag": "multi-word", "count": 2604 },
    { "tag": "generic", "count": 1190 },
    { "tag": "coined", "count": 638 }
  ]
}

Counts cover domains that are currently available and have been judged. Sorted by count, then alphabetically. Pass any tag back as ?tag= on /api/drops to filter the feed; unknown tags are ignored rather than erroring.

Add an email to the drop-alert list. Idempotent per address. Included for completeness — most API consumers won't need it.

curl -X POST "https://api.namedry.com/api/subscribe" \
  -H "Content-Type: application/json" \
  -d '{"email":"[email protected]"}'

{
  "subscribed": "[email protected]"
}

A malformed body returns 400 {"error":"invalid json body"}; a bad address, 400 {"error":"invalid email"}.