API

API access, honestly described

The API surface is designed but not yet public. This page describes what it would expose and what the shapes look like — it does not fabricate a live endpoint, a key, or a working call.

Status: not yet public

There is no live API today. Only a developer's endpoint URL scheme under /api/* exists as placeholders. Access is by request, granted individually, via the desk address.

Appraise

GET /api/appraise?name=<term>

Runs the same machine-checkable gates as the appraisal page. Response shape mirrors the appraisal structure: input, normalised name, TLD, length, syllables, a 0–100 score, a tier, and the per-gate checks (including the human judgement entries surfaced as manual flags, never scored).

Generate

POST /api/generate

Runs the construction engine and returns a shortlist of candidates sorted by score. Each candidate carries its root, suffix, phonotactic and neighbourhood numbers, and the morpheme story — the one-line “root + suffix” explanation the doctrine requires per candidate.

Availability check

GET /api/availability?name=<term>

Would return a per-TLD availability snapshot with an explicit re-check at the registry caveat, because every availability result is a snapshot and open seams close in days.

Requesting access

When the API opens, access will be granted case-by-case. To be considered, write the desk with your use case and volume: contact@domainvalue.com. There are no keys to request today.