1. Fetch the TLD collection with an authenticated catalogue-read credential. Follow returned pagination metadata until the selected inventory is complete.
2. Read the detail resource for a suffix when you need its stored offer and policy information.
3. Read effective pricing with the appropriate pricing scope. Keep the action, term, currency and applicable availability together in your own model.
4. Render only supported order choices. A missing two-year transfer price is not permission to multiply the one-year price and invent an offer.
5. For the actual domain and operation, query the registry requirements endpoint before submission. Use a current quote when options, promotions or rewards affect the total.

TLD detail describes the stored offer. The requirements endpoint supplies the active operation-specific fields and consent contract. A registration form and a transfer form for the same extension can therefore need different inputs. Validate the submitted form against the current operation rather than a generic contact template alone.

A local cache can improve browsing, but retain when it was fetched and refresh before placing an order that depends on changed eligibility or pricing. A successful search is not a reservation. Handle an unavailable or repriced order with a clear customer decision instead of silently substituting another term.

Keep customer-facing labels separate from API identifiers. Use returned suffix and resource values consistently, preserve multi-label extensions, and send full domain names to availability checks. If a suffix disappears for this account, investigate account scope or offer status; do not bypass the catalogue by repeatedly submitting an unsupported registration.

• Build domain forms from current registry field and consent requirements
• Create a domain-operation quote and keep its currency and expiry attached to the order
• Check domain availability with the Domain Nexus v2 API
• Consume the exact reseller pricing export without inventing unsupported terms