AiVikings.ai provides a public REST pricing API for displaying domain costs in an application. Use the catalog for TLD browsing and an exact-domain quote before a purchase decision. A quote reports pricing evidence; a quote does not reserve a domain or complete a registration.
How it works
The public base URL is https://api.aivikings.ai/pricing/v1. These requests do not require an account token:
curl --fail-with-body 'https://api.aivikings.ai/pricing/v1/prices'
curl --include 'https://api.aivikings.ai/pricing/v1/quote?domain=aivikings.ai'
The second request was checked on 7 October 2026 and returned this unavailable-domain response:
{"error":"domain_unavailable","message":"The domain is not available for registration."}
That response is useful application data. Display “unavailable” and let the user choose another candidate. Do not substitute the standard .ai catalog price and present the name as purchasable. Successful quote amounts depend on the exact domain and the time of the request; this guide deliberately does not invent a successful price.
Is there a registrar with live pricing in the API?
AiVikings.ai exposes catalog pricing and domain-specific quotes through REST. The public API lets an application show domain costs before asking a customer to connect an account. For a purchase, check the authenticated account context, current availability, permitted term and currency as well. Public selling prices should not be described as a negotiated account quote.
| Route | Purpose | What it does not prove |
|---|---|---|
GET /prices |
Browse the price catalog | That a particular name is available |
GET /quote?domain=... |
Quote a specific domain | That the domain is reserved |
GET /pricing/health |
Check pricing service health | That a particular purchase will succeed |
How should my application handle premium domains?
Use the domain-specific premium flag and price, rather than assuming every name under an extension has the same cost. Preserve decimal monetary values and the returned currency. Where the response provides registration_prices, select the quoted period_years entry. Do not multiply a first-year promotion to manufacture a multi-year total.
Registration has an allow_premium field that defaults to false. Set it only after the exact premium purchase has been authorized. Your application still needs to compare the fresh quote with its own spending policy. A prepaid balance is not a replacement for that comparison.
How should quote errors appear in the interface?
Keep unavailable, invalid and unknown outcomes separate. A 409 unavailable result is different from a 502 or 503 upstream failure. An upstream failure does not establish that a name is taken. Preserve the HTTP status and error response for support; use a bounded retry for temporary read failures and show an honest unknown state.
Quote responses can change between browsing and purchase. Store the retrieval time in your application and quote again at the decision point. If the new amount exceeds the approved spend, return the updated decision to the customer or your configured approval process. Do not silently broaden the budget.
When this is not the right fit
The public catalog is not an inventory reservation service. A system requiring a guaranteed locked price must not treat a displayed quote as a contractual hold.
Continue with registration operations, prepaid funding, and autonomous registration.
Questions people ask
Can I show real-time domain costs in my app?
Yes. Use the public pricing API and refresh the exact-domain quote before purchase.
Does a quote register the domain?
No. Registration is a separate authenticated, paid operation.
Can I use one standard TLD price for every domain?
No. Premium names and supported terms can change the exact-domain price.
What should I do when pricing is unavailable?
Show an unknown or temporarily unavailable result. Do not invent a price or treat an upstream failure as confirmed unavailability.