# RDAP Portfolio Change Receipts (`muazah/rdap-portfolio-receipts`) Actor

- **URL**: https://apify.com/muazah/rdap-portfolio-receipts.md
- **Developed by:** [muazah](https://apify.com/muazah) (community)
- **Categories:** Automation
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

$2.00 / 1,000 domain checkeds

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.

Learn more: https://docs.apify.com/actors/running/actors-in-store.md#pay-per-event

## What's an Apify Actor?

An Actor is a serverless cloud program that runs on the Apify platform. It has two run modes.
In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours,
and optionally produces a well-defined JSON output, datasets with results, or files in key-value store.
In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server.

Apify vocabulary and the platform model are defined once, in the agent quickstart at https://apify.com/agents.md.

## How to integrate an Actor?

If asked about integration, you help developers integrate Actors into their projects.
You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready.

Do not guess an integration path. Every one of them is in the agent quickstart at https://apify.com/agents.md: the Apify MCP server, Agent Skills with the Apify CLI, the JavaScript and Python clients, the REST API, and the account-free path for an agent with no human to sign in. It also carries the rule on stating cost before the first paid run.

For examples already wired to this Actor's own input schema, see the [API](#api) section below.

Each client library has reference documentation the quickstart does not restate: [JavaScript/TypeScript](https://docs.apify.com/api/client/js/docs.md) (`npm install apify-client`) and [Python](https://docs.apify.com/api/client/python/docs.md) (`pip install apify-client`).

# README

## RDAP Portfolio Change Receipts

Monitor a domain portfolio against live registry records and get receipts you can reconcile, one line per domain per run.

### What it does

- Checks up to 200 distinct domains per run against the authoritative RDAP service for each TLD (via the IANA bootstrap, longest-suffix routing, including multi-part TLDs like co.uk).
- Diffs registrar, nameserver set, domain status set, and the registry-published expiration date against your prior run.
- Emits expiry-window alerts at 90 / 30 / 14 / 7 / 1 days to the published expiration, firing once per crossing (no repeat storms).
- Flags `REGISTRATION_NO_LONGER_OBSERVED` only after two independent authoritative 404 observations with timestamps. Faults never count as confirmation, and failures never overwrite a good snapshot.
- Records what could not be verified: per-domain status (SUCCESS, NOT\_FOUND\_OBSERVED, UNSUPPORTED\_TLD, RATE\_LIMITED, FETCH\_FAILED, INVALID\_RESPONSE, INVALID\_INPUT, DUPLICATE\_INPUT), source URL, and billable flag.
- Metadata only. No WHOIS privacy redaction problems: it stores registrar name, nameservers, statuses, and event dates. Never registrant contacts.

### Input

`{"domains": [{"domain": "example.com"}], "monitorKey": "my-portfolio", "stateMode": "compare-and-save"}`

- **monitorKey** namespaces your stored snapshot. Run the same key repeatedly to get change receipts over time.
- **stateMode**: `compare-and-save` (default), `lookup-only`, or `reset-baseline`.
- Also accepts a multiline CSV (`domain,label`).

### Output

- **Dataset**: one observation row per input domain, plus change rows with before/after and the prior observation timestamp.
- **Run artifacts**: observations.csv and changes.csv in the run's key-value store.
- **Summary**: counts by status, billable domains, and the monitor key.

### Billing

Pay per distinct domain that returns a successful check or an authoritative 404 observation. Duplicates, unsupported TLDs, rate-limits, and fetch failures are not charged. Unchanged successful checks are billable (that is the check you paid for).

### Honest limits

- `NOT_FOUND_OBSERVED` is an authoritative absence at observation time. It is never a claim that a domain is available to register.
- Expiration is the registry-published event date, not a renewal or purchase promise.
- Some TLDs have no public RDAP service; those come back as UNSUPPORTED\_TLD, uncharged.

# Actor input Schema

## `domains` (type: `array`):

Domains to check: bare names, https URLs, or IDNs. Duplicates and aliases are deduped before charging.

## `domainsCsv` (type: `string`):

Optional multiline CSV 'domain,label'. Ignored if Domains array is set.

## `monitorKey` (type: `string`):

Namespaces the stored snapshot state. Run the same monitorKey repeatedly to get change receipts across runs.

## `stateMode` (type: `string`):

compare-and-save: diff against prior run and save. lookup-only: no state read/write. reset-baseline: wipe and re-baseline.

## `maxDomains` (type: `integer`):

Hard cap of 200 distinct domains per run.

## `includeUnchanged` (type: `boolean`):

Emit observation rows for unchanged domains too (recommended for reconciliation).

## Actor input object example

```json
{
  "domains": [
    {
      "domain": "example.com"
    },
    {
      "domain": "example.org",
      "label": "demo"
    }
  ],
  "monitorKey": "default",
  "stateMode": "compare-and-save",
  "maxDomains": 200,
  "includeUnchanged": true
}
```

# Actor output Schema

## `observationRows` (type: `string`):

One observation per input domain (status, registrar, nameservers, expiration, billable flag) plus change rows with before/after evidence.

## `summary` (type: `string`):

Distinct domains, billable domains, counts by status, change count and monitor key.

# API

You can run this Actor programmatically using our API. Below are code examples in JavaScript, Python, and CLI, as well as the OpenAPI specification and MCP server setup.

## JavaScript example

```javascript
import { ApifyClient } from 'apify-client';

// Initialize the ApifyClient with your Apify API token
// Replace the '<YOUR_API_TOKEN>' with your token
const client = new ApifyClient({
    token: '<YOUR_API_TOKEN>',
});

// Prepare Actor input
const input = {
    "domains": [
        {
            "domain": "example.com"
        },
        {
            "domain": "example.org",
            "label": "demo"
        }
    ],
    "monitorKey": "default",
    "stateMode": "compare-and-save",
    "maxDomains": 200,
    "includeUnchanged": true
};

// Run the Actor and wait for it to finish
const run = await client.actor("muazah/rdap-portfolio-receipts").call(input);

// Fetch and print Actor results from the run's dataset (if any)
console.log('Results from dataset');
console.log(`💾 Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`);
const { items } = await client.dataset(run.defaultDatasetId).listItems();
items.forEach((item) => {
    console.dir(item);
});

// 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/js/docs

```

## Python example

```python
from apify_client import ApifyClient

# Initialize the ApifyClient with your Apify API token
# Replace '<YOUR_API_TOKEN>' with your token.
client = ApifyClient("<YOUR_API_TOKEN>")

# Prepare the Actor input
run_input = {
    "domains": [
        { "domain": "example.com" },
        {
            "domain": "example.org",
            "label": "demo",
        },
    ],
    "monitorKey": "default",
    "stateMode": "compare-and-save",
    "maxDomains": 200,
    "includeUnchanged": True,
}

# Run the Actor and wait for it to finish
run = client.actor("muazah/rdap-portfolio-receipts").call(run_input=run_input)

# Fetch and print Actor results from the run's dataset (if there are any)
print(f"💾 Check your data here: https://console.apify.com/storage/datasets/{run.default_dataset_id}")
for item in client.dataset(run.default_dataset_id).iterate_items():
    print(item)

# 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start

```

## CLI example

```bash
echo '{
  "domains": [
    {
      "domain": "example.com"
    },
    {
      "domain": "example.org",
      "label": "demo"
    }
  ],
  "monitorKey": "default",
  "stateMode": "compare-and-save",
  "maxDomains": 200,
  "includeUnchanged": true
}' |
apify call muazah/rdap-portfolio-receipts --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,muazah/rdap-portfolio-receipts"
        }
    }
}
```

The hosted server signs you in with OAuth on first connect, so no API token belongs in this config. Clients without OAuth support can send an `Authorization: Bearer <APIFY_API_TOKEN>` header instead, using a token from API & Integrations in Apify Console (https://console.apify.com/settings/integrations).

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/actors/6pFoc1EIvOsWZEWsn/builds/YEjyodlNWuUI34mRg/openapi.json