Portfolio

spaceship portfolio

Operating a whole account rather than one domain. The constraint that shapes everything here is the API's rate limit asymmetry.

The budget that decides the approach

Looping domains get over an account burns the per-domain budget and stalls. The list endpoint returns 13 fields per domain, all of them required, which is enough to answer almost every portfolio question in ceil(total / 100) requests.

Fields on every row: name, unicodeName, isPremium, autoRenew, registrationDate, expirationDate, lifecycleStatus, verificationStatus, eppStatuses, suspensions, privacyProtection, nameservers, contacts.

Start here

spaceship portfolio lint --json

One or two requests for the whole account. Returns findings with a severity, the domain, a message, and a runnable fix. The envelope's result.requestsUsed reports what it cost.

spaceship portfolio rules --json     # what the seven rules check for
spaceship portfolio lint --rule expiring-without-autorenew --json

Lifecycle states are not one "expired"

lifecycleStatus distinguishes states whose recovery cost differs, and treating them as one loses the difference that matters:

A domain in redemption is urgent for a reason a date alone does not convey.

Reading expiry without inverting it

Expiry has a counterintuitive direction: a large number of days is good. When sorting or filtering, sort ascending by days remaining, and state the direction in words rather than showing a bare number.

spaceship domains list --json returns every domain sorted most urgent first.

Applying a change across many domains

There is no bulk write endpoint. Each domain is its own request against a 5-per- domain budget, so:

1. Get the target set from one portfolio lint or domains list call.
2. Preview one domain first, without --apply, and read the request it builds.
3. Apply per domain, pausing between them. A tight loop trips the limit and the CLI will retry with the API's Retry-After, which is slower than pacing.

# Which domains lack auto-renew, as a list of names
spaceship portfolio lint --rule expiring-without-autorenew --json \
  | jq -r '.result.findings[].domain'

Every finding already carries the exact command that fixes it in fix. Prefer running those over reconstructing the invocation.

Checking availability in bulk

spaceship domains check a.com b.dev c.io --json batches 20 names per request automatically. The result carries premiumPricing when a name is premium, so availability and price arrive together.

What this cannot do

• There is no transfer-out endpoint; the API exposes only the auth code and the lock, and direction has a single value, in.
• There is no bulk renew or bulk nameserver change.
• Deleting a domain has no documented rate limit and no undo.