Who Pays Whom?
The end customer pays the white-label operator through the operator's own rails: Stripe, Bitcoin, HNS, invoice, or another method. The operator pays HeadlessDomains the wholesale cost from prepaid GFA Gems.
Partner docs
How HeadlessDomains Partners works
These are the working terms for TLD owners and white-label registrar operators.
Core Terms
Namespace (TLD)The Handshake top-level name, such as .testjob or .defiwallet.
White-label registrarA partner-branded site where end customers search and buy names. The partner owns the brand, customer relationship, payment rails, and support.
Wholesale costThe USD price the white-label operator pays HeadlessDomains for each successful registration or renewal. It is not the retail price paid by the end customer.
Retail priceThe price the partner charges their customer through their own checkout. The partner decides this price.
GFA Gems balanceThe partner's prepaid balance. HeadlessDomains converts the USD wholesale cost into Gems at the GFAVIP conversion rate and debits Gems after provisioning succeeds.
API keyA secret token for partner-owned frontends, payment callbacks, or admin tooling to check availability, register names after payment, and read balance.
Registration inventoryRead-only Partner API endpoints for downstream dashboards and AI agents to list registered names and inspect backend registry references without exposing customer email.
Registry source of truthHeadlessDomains Partners stores the domain list, billing ledger, provisioning state, and links to registry/DNS backend records. SkyInclude/registry-dash remains the registry execution layer where appropriate.
InteroperabilityAn optional namespace owner toggle. When enabled, approved registrar channels may list the namespace. It starts off by default.
Catalog namespaceA namespace the partner does not own but has permission to sell, such as HeadlessDomains-owned .agent, .chatbot, or future HeadlessDomains launches.
Preview Registrar
After creating a white-label site, open the partner detail page and click Preview registrar. That preview shows the customer-facing search page and namespace selector.
Custom Frontends
Partners can skip the hosted starter UI and build their own frontend with the API key, preflight endpoint, registration endpoint, and their own payment flow.
Frontend integration guide Copy-paste guideCatalog Access
HeadlessDomains can grant a seller permission to add approved catalog namespaces to their account. The seller collects retail payment, and their prepaid Gems balance pays the wholesale cost.
DNS Safety
DNS and nameserver writes need separate scopes, module approval, backend support, and audit logs before partners or AI agents can mutate records.
DNS safety designRegistrar API
The HTTP registry command surface for registrar integrations before EPP, including a machine-readable OpenAPI spec.
Registrar API docs Handoff packet OT&E checklist Evidence template EPP gateway contract EPP conformance checklistFramework Standard
The shared product language for packages, modules, source access, partner responsibilities, HeadlessDomains responsibilities, and launch boundaries.
Partner framework standardPackages And Modules
The partner-facing menu for Hosted Starter, Framework Partner, API-only, Custom / Enterprise, and registrar module scope.
Package menuCommercial Defaults
Draft operating defaults for setup fees, monthly minimums, pilot waivers, and cancellation recovery before final approval.
Commercial policyDownstream Repos
The contribution and update workflow for partner-specific registrar repos, AI-agent pull requests, upstream template updates, and safe secret handling.
Downstream workflowRailway Deployment
The production startup path runs database migrations before Gunicorn so schema changes deploy with the app.
Deployment guidePilot Launch Runbook
The operator checklist for commercial, namespace, registrar, API, downstream smoke, and support gates before launch approval.
Launch runbook