# Quiet File Team Setup Kit Generator (`pandadad0214/quiet-file-team-setup`) Actor

Generate a configured Quiet File Team starter ZIP (several bots sharing one computer through files) with rules, guided install and acceptance checks. $29 per generated kit; the free core is github.com/pandadad0214/quiet-file-team. Not a scraper.

- **URL**: https://apify.com/pandadad0214/quiet-file-team-setup.md
- **Developed by:** [Panda Federation](https://apify.com/pandadad0214) (community)
- **Categories:** AI, Developer tools, Automation
- **Features:** Limited permissions
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

$29.00 / complete setup kit

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

## Quiet File Team Setup Kit Generator

Generate a configured Quiet File Team starter ZIP (several AI bots sharing one computer through files) with ready rules, guided installation, examples and acceptance checks. $29 per successfully generated kit; no scraping and no model calls.

### How to use this

1. Fill **Roster** (`TEAM_IDS`, default `lead builder helper`), **IANA time zone** (`TEAM_TZ`, default `UTC`) and keep **Coordinator** as `lead` (it must be on the roster). `displayName` is an optional generic label.
2. Allow a maximum run charge of at least $29 (one `setup_kit` event per successful kit; nothing is charged for failed validation or generation) and click **Start**.
3. Download **OUTPUT.zip** from the run's key-value store, extract it to a NEW local folder, review `team.conf`, then follow `guidance/references/install-guide.md` and the acceptance checklist. The kit does not install schedules or run agents.

### For AI agents

| Field | Value |
| --- | --- |
| Purpose | Generate a configured file-first team kit ZIP (core scripts + guidance) from a roster, time zone and coordinator. |
| Use when | A user wants a ready-to-unpack Quiet File Team folder instead of configuring the free core by hand. |
| Do not use when | The free core is enough (`git clone https://github.com/pandadad0214/quiet-file-team`), or you need scheduling, hosting or messaging. |
| Inputs | `TEAM_IDS`, `TEAM_TZ`, `coordinator` (`lead`), optional `displayName` |
| Outputs | `OUTPUT.zip` in the key-value store; dataset row with archive key, roster, zone, coordinator, edition note and checksum |
| Cost | $29 per successfully generated and persisted kit (`setup_kit`). |

### Switch editions

**Free path:** `git clone https://github.com/pandadad0214/quiet-file-team.git`, set `TEAM_DIR` to the new checkout and follow its README. No purchase is needed for the core.

**Free → paid generator:** on this page enter roster and zone, keep lead, allow at least $29, run and download OUTPUT.zip. It includes the free core plus optional paid guidance. Deploy in a separate directory and practice before adopting. Environment overrides still win over generated config defaults. The fictional exercise uses the default roster even if your configuration differs.

**Paid → free:** back up existing data, install a clean free clone separately, review/re-enter active tasks deliberately and repoint routines. Remove optional guidance if unwanted; never overwrite operational logs with examples. Other editions: a free MCP companion (github.com/pandadad0214/quiet-file-team-mcp) and a $29 one-time Agensi setup skill (agensi.io/skills/quiet-file-team-setup-kit) that guides your agent through the same setup in your own folder.

### Boundaries

One trusted shared Linux machine, Bash 4+, GNU tools and reliable local flock locks. Test suite uses ripgrep. Not remote transport, access control, encrypted storage, a scheduler or a hosted team. Roster labels do not authenticate identities. Only lead has coordinator authorization. Never put personal data or credentials in the bus. Input validation is a bounded syntactic guardrail, not a complete private-data detector.

### For developers

`src/generator.py` is pure bounded generation; it never executes caller input. Assets are copied only from the generic free source and guidance draft, never an operational team. `src/main.py` persists and reads back the ZIP, persists dataset metadata, then calls `Actor.charge(event_name='setup_kit', count=1)` exactly once. A budget check occurs before persistence. No charge is made for input validation, generation or persistence failures. Distributed billing is not an atomic transaction: a billing rejection can leave a persisted kit, and a platform interruption after charging is governed by Apify; no refund promise is made.

Tests: `python -m unittest discover -s tests -v`. Local generation: `python -m src.local OUTPUT.zip`. Local generation makes no platform call or charge.

# Actor input Schema

## `TEAM_IDS` (type: `string`):

1–12 unique lowercase ids, 1–24 characters each; lead is required. Free: clone https://github.com/pandadad0214/quiet-file-team.git and follow README. Paid generator: enter roster and zone, keep lead coordinator, run once and download OUTPUT.zip; use a new folder. Back to free: retain existing data, use a clean clone and repoint routines after review.

## `TEAM_TZ` (type: `string`):

Use a supported IANA zone. Do not change zones in existing logs. Free: clone https://github.com/pandadad0214/quiet-file-team.git and follow README. Paid generator: enter roster and zone, keep lead coordinator, run once and download OUTPUT.zip; use a new folder. Back to free: retain existing data, use a clean clone and repoint routines after review.

## `coordinator` (type: `string`):

Must be in roster. Authorization remains lead-only; ids do not authenticate users. Free: clone https://github.com/pandadad0214/quiet-file-team.git and follow README. Paid generator: enter roster and zone, keep lead coordinator, run once and download OUTPUT.zip; use a new folder. Back to free: retain existing data, use a clean clone and repoint routines after review.

## `displayName` (type: `string`):

Non-sensitive plain label, no email or credentials. Used only in metadata, never shell code. Free: clone https://github.com/pandadad0214/quiet-file-team.git and follow README. Paid generator: enter roster and zone, keep lead coordinator, run once and download OUTPUT.zip; use a new folder. Back to free: retain existing data, use a clean clone and repoint routines after review.

## Actor input object example

```json
{
  "TEAM_IDS": "lead builder helper",
  "TEAM_TZ": "UTC",
  "coordinator": "lead"
}
```

# Actor output Schema

## `archive` (type: `string`):

No description

## `metadata` (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 = {};

// Run the Actor and wait for it to finish
const run = await client.actor("pandadad0214/quiet-file-team-setup").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 = {}

# Run the Actor and wait for it to finish
run = client.actor("pandadad0214/quiet-file-team-setup").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 '{}' |
apify call pandadad0214/quiet-file-team-setup --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,pandadad0214/quiet-file-team-setup"
        }
    }
}
```

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/ZfuWLWBkTM9FqlK8Q/builds/nnDWAbDIdCb6AOyQM/openapi.json