# Redirect Map Preflight (`immemorial_sarinda/redirect-map-preflight`) Actor

Offline structural checks for an authorized CSV redirect plan: duplicate mappings, conflicts, cycles and chains. No URL fetching or server changes.

- **URL**: https://apify.com/immemorial_sarinda/redirect-map-preflight.md
- **Developed by:** [Picknotes](https://apify.com/immemorial_sarinda) (community)
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

$100.00 / 1,000 complete redirect reports

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

## Redirect Map Preflight

Check a supplied redirect plan before a separate deployment. Find duplicate or conflicting mappings, cycles and chains using literal URL matching. This service does not install redirects or inspect your server.

#### Input and limits

Own mode fields: useDemo=false, authorizedNonpersonalNonconfidentialData=true, and redirectCsv containing the exact CSV text. The header must be exactly source,target in that order. No column mapping or trimming is performed.

Limits: at most 1 MiB of decoded input, 1,000 logical data records after the header and 8,192 characters per URL. Only the supported ASCII absolute HTTP(S) URL profile is accepted. No normalization, IDN conversion, wildcard rules, fragments or userinfo. Token-bearing URLs remain prohibited even if their syntax is accepted.

This is a structural report, not a live-URL or server-correctness check. No crawling, DNS resolution or fetching of supplied URLs occurs. Paths exceeding 64 sampled nodes and omitted/truncated detail make a report incomplete and ineligible for delivery. The output retains literal URLs. It is not a complete per-edge migration approval ledger.

The raw request envelope is also limited to 1,200,000 bytes. Native output is limited to 2 MiB and the full serialized one-item dataset POST, including its array wrapper, to 4,500,000 bytes. Outputs are not truncated to force a successful delivery.

#### Synthetic example

Use this input to run the bundled fictional fixture through the same analysis path:

```json
{"useDemo": true}
```

Expected report excerpt from the saved synthetic golden (not a newly executed hosted result):

```json
{
  "schema_version": 1,
  "status": "diagnostics",
  "complete": true,
  "analysis_complete": true,
  "details_complete": true,
  "summary": {
    "chains": 2,
    "conflicting_sources": 1,
    "cycles": 2,
    "duplicate_extra_records": 1,
    "duplicate_groups": 1,
    "invalid_records": 0,
    "records": 11,
    "records_complete": true,
    "unique_edges": 10,
    "valid_records": 11
  }
}
```

#### Price and completed reports

Price: **US$0.10 per complete report**, including the synthetic demo. Findings in a complete report are still a completed service. Unsupported, incomplete or invalid results are not delivered as partial paid reports. Platform usage is included and there is no startup charge.

The Actor attempts one full-output dataset item. If Apify accepts that item, a completion charge can occur even if the run later fails or its acknowledgement is lost. Do not automatically rerun an uncertain delivery. The embedded receipt describes expected billing and output identity; it is not proof of settled charges or revenue.

#### Data and report download

Submit only data you have permission to process that is nonpersonal and nonconfidential. Do not include credentials, tokens or secrets. Apify stores input before execution. This service does not promise anonymization, secret detection, deletion, private storage or a particular retention period.

Download the full raw default-dataset JSON, without cleaning, field selection, flattening or unwinding. The dataset contains one full report plus provenance and receipt fields. The matching helper accepts one item or a singleton array and writes exact REPORT.json bytes after validation:

```
python3 -B extract_report.py dataset.json new-output-directory
```

Use a new output directory under an existing trusted POSIX parent. Symlink input/output paths and overwriting existing destinations are unsupported. The helper uses Python’s standard library; Windows is unsupported. A late filesystem failure may leave an incomplete new directory. Hash/structure validation does not authenticate the sender or prove the original input was true. Use the helper’s included terms; no additional support or refund promise is made here.

Helper download: [redirect-report-helper-0.1.4.zip](https://api.apify.com/v2/key-value-stores/f7yuJ759tlYrp43zi/records/redirect-report-helper-0.1.4.zip). ZIP SHA-256: `3808cdd00dee569fadad6b40c3cc9a0f6cba9c2d116f1227e455cdd39795f6ab` (8,983 bytes). Unpack all four files and read README.md and TERMS.md.

# Actor input Schema

## `authorizedNonpersonalNonconfidentialData` (type: `boolean`):

Own mode requires true for authorized, nonpersonal, nonconfidential data.

## `redirectCsv` (type: `string`):

Own mode only; literal authorized text, never a URL. Leave absent in demo. Runtime enforces byte, structure and aggregate bounds. Static analysis; no URL fetches.

## `useDemo` (type: `boolean`):

Run bundled synthetic fixtures using the real engine. All own-data fields must be absent.

## Actor input object example

```json
{
  "authorizedNonpersonalNonconfidentialData": false,
  "useDemo": true
}
```

# Actor output Schema

## `results` (type: `string`):

No description

# 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 = {
    "useDemo": true
};

// Run the Actor and wait for it to finish
const run = await client.actor("immemorial_sarinda/redirect-map-preflight").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 = { "useDemo": True }

# Run the Actor and wait for it to finish
run = client.actor("immemorial_sarinda/redirect-map-preflight").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 '{
  "useDemo": true
}' |
apify call immemorial_sarinda/redirect-map-preflight --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,immemorial_sarinda/redirect-map-preflight"
        }
    }
}
```

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/DZOQdXelAXJTl7yRz/builds/en4uhU9hTnyuyeT9n/openapi.json