AiVikings.ai gives MSPs API and MCP access to domain inventory, renewals, nameservers and DNS workflows. Start client onboarding with an evidence-based inventory and explicit ownership mapping before automating changes. The same records should support renewal planning, incident recovery and a future client handover.
An MSP often inherits a mixture of registrar accounts, historical contacts and DNS providers. A domain might support a website, email, identity verification and remote access at the same time. That makes domain administration a service-continuity task as much as a purchasing task. The goal is to know who controls each layer and what needs to remain working.
How it works
For holdings in the authorized AiVikings.ai account, start with a read-only inventory:
curl --fail-with-body https://api.aivikings.ai/v1/domains \
-H "Authorization: Bearer $AIVIKINGS_TOKEN"
The response provides a domains array. The portfolio review example reports saved expiry dates and flags missing dates for review. A missing date is not evidence that a domain never expires. The example's fixture mode uses synthetic records so the report can be tested without customer credentials.
For domains outside the connected account, document the current provider and authorized access process. Do not imply that one API token grants visibility across every registrar used by an MSP's clients. The inventory must identify the boundary of the data actually retrieved.
How should an MSP onboard a client's domains?
Record each domain's intended holder, managing account, expiry evidence, authoritative DNS provider and service dependencies. AiVikings.ai can provide account-owned domain facts, while the MSP supplies the client mapping and service context. Keep unknown fields visible and assign follow-up work instead of filling them with assumptions from a project name or invoice.
Use separate columns for the client organization, registrant contact and internal service owner. Those roles may coincide, but they should not be silently merged. Also identify who can authorize a renewal, a nameserver change or a transfer. A support technician's access to a ticket does not necessarily establish authority for all three.
Preserve the source and collection time of each important fact. A saved expiry value is useful for prioritization; a fresh status check provides better evidence for an imminent renewal decision. A historical screenshot can explain a past incident without proving the current state.
Can renewals be managed through code instead of yearly logins?
AiVikings.ai supports programmatic renewals through REST and MCP. An MSP can build a review queue, obtain current pricing and execute the authorized subset. The workflow still needs sufficient prepaid funds, the correct client context and verification of the new expiry. A scheduled job running successfully does not prove that every domain in the batch renewed.
Keep renewal candidates separate from renewal approvals. The renewal review guide explains why missing prices, client offboarding and uncertain ownership should block or divert individual rows rather than disappear from the report.
Record per-domain outcomes. If nine renewals complete and one remains unknown, report that exact state. Repeating the entire batch can obscure which requests were already accepted. A client-facing report should distinguish confirmed renewal, explicit rejection and investigation needed.
How do I keep DNS changes within the client's scope?
Resolve the domain from an authorized client inventory and inspect the authoritative zone before editing records. AiVikings.ai supports nameserver and DNS operations, but a token's technical access does not replace your service agreement. Validate the intended domain, record and change authority at the application boundary before a tool executes the write.
During onboarding, capture a record inventory and service map. An A-record change for a website should not remove mail or verification records. A nameserver migration affects the whole zone's authority, so it needs a broader review than a single-record update.
The DNS orchestration guide shows separate checks for registration, delegation, records and HTTPS. Use the checks appropriate to the client's services rather than reducing the domain to a green “website online” indicator.
What should a domain handover include?
Prepare a domain-by-domain record of holder responsibility, account ownership, expiry, renewal policy, nameservers, DNS provider and service dependencies. Include the supported process for moving control and the date each part was verified. A list of domain names without those responsibilities leaves the next operator to rediscover the important facts.
Do not email raw registrar tokens as a substitute for an account handover. Use the supported access, account or transfer process and revoke obsolete access after the agreed transition. Sub-customer support alone does not prove that a particular account-push mechanism exists; verify the required handover operation before promising it to the client.
Keep the commercial end date separate from domain expiry. A service agreement ending next week does not mean the client's domain should expire next week. Clarify who funds and authorizes the next renewal during the transition.
How should an MSP use AI assistants for this work?
Use an assistant to inspect evidence, prepare review tables and propose constrained changes, with actual tool results behind factual claims. AiVikings.ai supports connected assistants through MCP. For write operations, keep account selection, tenant boundaries and purchase policies in application controls as well as in the task prompt.
An inspection task can ask the assistant to flag domains approaching expiry, missing contacts or inconsistent nameservers. Require the assistant to label unknown facts. A plausible explanation for an inconsistency is a hypothesis until the relevant account or DNS evidence confirms it.
When this is not the right fit
This workflow does not replace a full MSP service desk, asset inventory or contractual handover process. It supplies the domain operations layer and the evidence needed to integrate that layer into those systems.
Continue with customer mapping, prepaid funding and portfolio management.
Questions people ask
Can an MSP manage renewals through code?
Yes. AiVikings.ai supports authenticated renewal operations, with prepaid funding and per-domain verification.
Can one account inventory prove ownership across all registrars?
No. Record which account and provider supplied each fact and investigate domains outside that scope.
What should happen to missing expiry dates?
Keep them visible as unknown and obtain current evidence before making renewal decisions.
Does sub-customer support guarantee a particular handover method?
No. Verify the supported account or transfer process for the required transition.
Can an assistant update client DNS?
Yes, through authorized tools, with client boundaries and exact change authority enforced by the workflow.