Discovery references
- Complete registration OpenAPI
- Supported TLDs as JSON and Markdown
- Canonical skill repository
- Existing DomainHelp x402 metadata
The storefront describes the flow. Transaction requests go to the existing API. A human page, Markdown document, or TLD record is not an executable registration endpoint.
Verified execution endpoints
| Action | Existing API |
|---|---|
| Availability lookup | GET / POST https://app.domainhelp.com/api/v1/domain-availability |
| Requirements & quote | GET https://app.domainhelp.com/api/v1/register-domain/requirements?domain=FULL_DOMAIN |
| Prepare order | POST https://app.domainhelp.com/api/v1/registration-orders |
| Pay & register | POST https://app.domainhelp.com/api/v1/register-domain |
| Private order status | GET https://app.domainhelp.com/api/v1/registration-orders/{id} |
Follow the order lifecycle
- Inspect and quote. Check the inventory, then obtain current requirements for the full domain. Availability lookup is a separate paid product.
- Authorize and validate. Obtain human approval for the total/term and agreement. Collect accurate registrant data and required registry fields. Follow the returned email-check mode.
- Prepare once. Use a private random 32-byte hex order token and a unique 16–200-character Idempotency-Key. Preparation does not purchase anything.
- Pay on that order. POST only the prepared
order_idwith the bearer order token. Use a standard x402 SDK to satisfy the actual challenge. - Verify and deliver. Poll the returned status URL, retain the payment receipt and recovery key, and confirm registration and easyDNS account handoff separately.
Retry the order, not the purchase. A 202, lost response, or uncertain registration outcome must be reconciled on the original order. Never create another paid order to recover it.
Payment and authorization
Discovery currently advertises x402 v2 exact on Base mainnet with USDC. The live quote and payment challenge supply the authoritative network, asset and total. The paying wallet must match the prepared payer and does not replace the end user’s registrant identity.
Verification is handled by the existing service. Exact deployed facilitator configuration is TBD — requires operator confirmation; follow the canonical skill rather than introducing another payment backend.
Credentials, recovery and limits
Keep order tokens, verification credentials, payment material and recovery keys private. After settled payment and confirmed registration, save the returned recovery key durably where the customer can retrieve it independently of email. Do not log contacts or secrets to public analytics.
One domain per order. Standard API limits and email-check limits apply; respect rate-limit responses. Use the published schema for validation errors and status details.
Confirm your registrant contact email
If this is a new or unverified registrant contact for a generic TLD, you will also receive a separate contact-verification email as part of ICANN’s Whois Accuracy Program. You must follow the individual link in that email and confirm your contact information by the deadline shown.
The confirmation page is hosted at https://approve.domainadmin.com. Use the link in your actual email to reach your verification page. Failure to complete verification can result in domain suspension.
This confirmation is separate from the email check during order preparation and from easyDNS welcome or account-delivery emails. Successful payment, registration or account delivery does not confirm that this step is complete. Contacts already verified may not need another check; ccTLD requirements can differ.
ICANN contact-verification requirements
DNS management after delivery
Set up easyDNS API access in the customer account. The official easyDNS MCP project provides subsequent DNS-management tools and its own setup guidance. It is a separate integration from buying the domain; keep credentials private and scope changes to authorized domains.
Keep renewals explicit
Recurring x402 renewal is planned, not available in this release. Renew through the easyDNS account before expiry; see renewal help. The quickstart and catalog snapshots are reference documents; always request current requirements before spending.