Each item contains domain, operation and its payload. The planner recognises availability, register, renew, transfer, auto_renew, let_expire, lock, privacy, contacts, nameservers, dns_template, dns_record, domain_forwarding and reseller_push. Actual provider and account capabilities still determine which work can execute.

For example, a proposed lock request for a domain you own has this shape:

{
  "requests": [
    {"domain": "example.com", "operation": "lock", "payload": {"enabled": true}}
  ],
  "chunk_size": 100
}

The selection can contain up to 10,000 operation objects. Chunk size is bounded from 1 to 500. Duplicate domain, operation and payload combinations are rejected. The planner skips register or transfer items already owned, and skips operations on unowned domains when ownership is required.

1. POST the explicit requests to portfolio/preview with an idempotency key.
2. Inspect executable items, skipped reasons, provider grouping, risk and reversibility indicators, chunk count and approval requirement.
3. Compare the selected domains with your customer inventory. Correct omissions, unintended duplicates and ownership changes before proceeding.
4. Obtain current financial quotes separately for charged operations. The REST preview does not supply a complete live pricing check for every item.
5. POST the reviewed requests to portfolio/jobs with a meaningful name. The server recomputes the plan; read and review the stored job before approval.

• Approve the exact portfolio digest and start durable execution
• Create a domain-operation quote and keep its currency and expiry attached to the order
• Build and validate a reviewable DNS changeset
• Retry one failed portfolio item and export a reconciled outcome report