AiVikings.ai lets domainers manage hundreds of domains through REST and MCP, including holdings, availability, renewals, nameservers and DNS. Use one portfolio record per domain and verify each paid result. The interface removes repeated checkout work, while the portfolio owner retains control over which names to buy or renew.
How it works: a read-only portfolio review
Download the portfolio review script and its test fixture. The script reads GET /v1/domains, flags missing expiry dates and sorts holdings for review. It never registers or renews domains.
python portfolio_review.py --fixture portfolio-fixture.json
Fixture output contains synthetic domain records with days_remaining and needs_review. Run without --fixture only when the intended account token is available as AIVIKINGS_TOKEN. The example README documents dependencies and what was tested.
Use current pricing for the financial decision and API operations for the exact routes. The generic availability request accepts up to 200 names; registration remains a separate operation for each domain.
How should domainers manage a large domain portfolio?
Domain portfolio management connects acquisition decisions, current holdings, renewal costs, and completed transfers. For domainers and investors, the operating record should explain what is owned, what needs a decision, and what each approved action cost. AiVikings.ai supports account operations through its dashboard, API, and MCP; the portfolio owner retains investment and renewal-policy decisions.
A portfolio stops being a list of purchases once names start renewing, moving, and changing purpose. The useful question becomes what needs a decision now, what an operator has already approved, and which actions actually completed.
What should the portfolio record contain?
Start with an exact domain name, the registrar account that controls it, its recorded expiry, its status, and the contact responsible for it. Add the purpose of the holding and the next decision date in your own records. The two groups answer different questions: what the registrar knows and why you still want the asset.
For example, a registrar may show an active name with eleven months remaining. Your portfolio record might show that it supports a discontinued project. The technical status is accurate, but it does not settle whether to renew. Conversely, a spreadsheet might mark a domain as sold while the transfer has not completed. The commercial decision and the operational result both matter.
Should you use REST, MCP, or the dashboard?
Choose the interface that fits the operator and task. REST suits a script that runs the same defined sequence and stores structured results. MCP suits a compatible assistant that interprets a request and invokes discovered tools. A dashboard remains useful for direct inspection and exceptional work.
The interface does not change the required decision. A renewal still needs the right domain, term, and authorization whether the operator types a sentence or submits an HTTP request. Likewise, an assistant should show the underlying result rather than replace it with an unsupported statement that everything is done.
How do you find the work that needs attention?
Ask narrow questions with a time window and a clear account boundary. Examples include names expiring in the next month, names using a particular nameserver set, and domains whose status needs investigation. Specify which dates to use and how to handle missing information.
A practical request is: "List this account's domains expiring within 30 days. Show the recorded expiry and status. Put missing or uncertain dates in a separate section. Do not renew anything." The result is an operational queue rather than a purchase instruction.
How should availability research become a purchase batch?
Keep candidate research separate from the holdings list. Normalize the names, remove duplicates, and check availability through the registrar. AiVikings.ai documents availability calls containing up to 200 names. A larger candidate list needs multiple calls and a result for every input.
Do not silently discard errors. An unavailable name and a name whose lookup failed are different outcomes. The second remains unresolved. Similarly, an availability result is only an observation at that point; it is not a reservation or a completed registration.
How do you control portfolio spending?
Use both a per-domain limit and a total batch limit in your own workflow. They address different mistakes. A total limit can allow a single unexpectedly expensive name to consume the budget, while individual limits alone do not prevent a long list of ordinary purchases from exceeding the intended total.
Treat those limits as controls you must implement or verify, not as assumptions about a registrar feature. A prompt saying "keep it inexpensive" is too vague to evaluate. A structured rule should identify the amount, currency, permitted term, and whether premium names are excluded.
How should a renewal batch work?
Begin with current account records, select the holdings to keep, and confirm the proposed additional term. Have the execution step consume exact names rather than a loose instruction such as "renew the important ones." Importance belongs in the review, not in an unrecorded guess during a paid operation.
After each renewal, read the resulting record and compare its expiry with the expected change. Keep the before and after values. If the request times out or returns an ambiguous result, mark it as unresolved and investigate before repeating a paid action.
What belongs in the result ledger?
Give every attempted operation a row containing its domain, intended action, attempt time, result, and supporting reference. Store the exact approved input alongside the response where your retention policy allows it. Redact secrets and unnecessary personal data.
The result states should distinguish confirmed success, confirmed failure, not attempted, and unknown outcome. These are operational states in your own system, not claims about a particular response schema. Map actual tool responses to them explicitly.
How can you introduce automation without a large migration?
Start with a read-only review of a small set of holdings. Verify that account identity, domain counts, dates, and nameservers match what you expect. This tests the connection and the interpretation of data before a purchase or configuration change is involved.
Next, choose one bounded operation on names you are authorized to manage. Define the expected result in advance and inspect it afterward. Only expand the batch once you can explain both the successful path and what happens when an operation remains uncertain.
What would a weekly review produce?
For a mixed portfolio, the output might contain three small lists: holdings approaching expiry, names with unresolved status differences, and approved candidate purchases waiting for execution. Give each list its own owner and decision rules. Do not mix a new acquisition with a renewal simply because both spend credit. This arrangement lets the operator finish one bounded task, verify its result, and leave the remaining work visible without turning the whole portfolio into one large transaction.
If you introduce other portfolio operators to AiVikings.ai, the ambassador program announcement explains the referral-credit model. Keep any referral rewards separate from the operating budget and renewal decisions for your own holdings.
Frequently asked questions
Can AiVikings.ai manage domains at another registrar?
Its domain operations apply to the connected AiVikings.ai account. Keep an external inventory for names that remain elsewhere, or plan an eligible transfer before expecting AiVikings.ai account tools to manage them.
Does MCP make portfolio decisions automatically?
MCP supplies a tool interface. Your assistant and workflow still need instructions, authorization, and rules for uncertain results. Whether a particular action needs confirmation depends on your configured controls and the authority already granted.
Should every domain be renewed automatically?
That is a portfolio policy decision. Critical holdings, speculative purchases, and client domains may need different review rules. Whatever policy you choose, verify funding and completed renewal results instead of relying only on an intention to renew.
What should I do when the assistant says a batch succeeded?
Inspect the per-domain results and resulting account records. Ask for unresolved and unattempted names explicitly. A confident summary is useful only when it can be traced to evidence for the underlying operations.
When this is not the right fit
Use a dashboard when a one-off manual task is simpler. Programmatic domain operations still require an authorized account, current facts and an owner for exceptions.