# Data Fixture Lab (staging test) (`abundant_naphtha/staging-data-fixture-lab`) Actor

Staging-only developer UX fixture for deterministic data processing (normalize, summarize, generate) of up to 25 records. Writes dataset rows and a SUMMARY record; no scraping or external requests. Not a production service.

- **URL**: https://securitybyobscurity.apify.com/abundant_naphtha/staging-data-fixture-lab.md
- **Developed by:** [Jaroslav Hejlek](https://securitybyobscurity.apify.com/abundant_naphtha) (community)
- **Features:** Limited permissions
- **Stats:** 1 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $0.01 / 1,000 results

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://securitybyobscurity.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://securitybyobscurity.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

## Data Fixture Lab (staging test)

A small deterministic data-processing Actor used to test the Apify developer experience on staging. It does not scrape websites or make external requests. It is a test fixture, not a production service.

### Operations

- `normalize`: preserve input order and fill missing record identifiers and labels.
- `summarize`: sort normalized records by value.
- `generate`: produce deterministic records from a seed.

Each run processes at most 25 records. Input records may be numbers or objects; the input form and runtime validation enforce the supported limits.

### Outputs

The dataset contains processed rows. The default key-value store contains `SUMMARY`, including item count, sum, mean, and status. For the verified input `[1, {"id":"a","value":3}, 2.5]`, the staging run produced three rows and a sum of 6.5.

### Failure testing

Setting `simulateFailure` writes the outputs and then exits with an intentional failure. This is useful for testing failure handling and storage inspection.

### Pricing and limitations

The current listing uses platform usage pricing. No custom paid event is configured. There is no scraping, request queue, standby server, schedule, or webhook configured. This Actor has been built and run on the staging platform; its public listing is intended for developer UX testing only.

# Actor input Schema

## `operation` (type: `string`):

normalize keeps input order and fills missing ids. summarize sorts rows by value. generate ignores record values and builds rows from seed.

## `records` (type: `array`):

At most 25 items. Each item is a finite number, or an object with a numeric value and optional id and label. Required for normalize and summarize. Generate accepts an empty array.

## `generateCount` (type: `integer`):

Row count used only when operation is generate. Minimum 1, maximum 25. Defaults to 5.

## `seed` (type: `integer`):

Starting state for generate. Stored on SUMMARY for every operation. Defaults to 1.

## `runLabel` (type: `string`):

Short label copied onto SUMMARY. Lowercase letters, digits, and hyphens. Must start with a letter or digit.

## `simulateFailure` (type: `boolean`):

When true, rows and SUMMARY are written first, then the Actor exits with code 1. The run status is FAILED. This is a controlled error-UX check, not a real fault.

## Actor input object example

```json
{
  "operation": "normalize",
  "records": [
    1,
    {
      "id": "a",
      "label": "alpha",
      "value": 3
    }
  ],
  "generateCount": 5,
  "seed": 1,
  "runLabel": "fixture-lab",
  "simulateFailure": false
}
```

# Actor output Schema

## `rows` (type: `string`):

One row per normalized or generated item. The overview view is selected by default.

## `summaryCollection` (type: `string`):

Key-value store keys in the summary collection.

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

The SUMMARY JSON record.

# 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 = {
    "operation": "normalize",
    "records": [
        1,
        2,
        {
            "id": "a",
            "label": "alpha",
            "value": 3
        }
    ],
    "generateCount": 5,
    "seed": 1,
    "runLabel": "fixture-lab"
};

// Run the Actor and wait for it to finish
const run = await client.actor("abundant_naphtha/staging-data-fixture-lab").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 = {
    "operation": "normalize",
    "records": [
        1,
        2,
        {
            "id": "a",
            "label": "alpha",
            "value": 3,
        },
    ],
    "generateCount": 5,
    "seed": 1,
    "runLabel": "fixture-lab",
}

# Run the Actor and wait for it to finish
run = client.actor("abundant_naphtha/staging-data-fixture-lab").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 '{
  "operation": "normalize",
  "records": [
    1,
    2,
    {
      "id": "a",
      "label": "alpha",
      "value": 3
    }
  ],
  "generateCount": 5,
  "seed": 1,
  "runLabel": "fixture-lab"
}' |
apify call abundant_naphtha/staging-data-fixture-lab --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,abundant_naphtha/staging-data-fixture-lab"
        }
    }
}
```

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-securitybyobscurity.apify.com/settings/integrations).

## OpenAPI specification

Download the OpenAPI definition: https://api-securitybyobscurity.apify.com/v2/actors/DEfwtudDDJ9AVRved/builds/KDkD8R0rxGoKEKjQO/openapi.json
